archive-ca.com » CA » D » DEFUNCT.CA

Total: 226

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Using nova-network’s multi_host to remove SPOF | boompty boomp
    prot opt in out source destination 0 0 DNAT tcp any any anywhere 169 254 169 254 tcp dpt www to 192 168 0 1 8773 and this allows cloud init on the Ubuntu instances to grab whatever it is they re grabbing from the EC2 API running on the controller When the Ubuntu instances boot but can t hit the EC2 API I have 192 168 0 1 assigned to my controller which runs the EC2 API cloud init seems to spin forever and the instances never really seems to boot If you uninstall cloud init the instances will boot but configuration does not appear to be complete ie missing ssh keys in etc ssh I tried using my controller s public IP or the controller s 10 176 65 54 address but neither seemed to work The latter is understandable as the instance will not be able to hit 10 176 65 54 since it s not attached to that network but it was my understanding that it should be able to hit the external IP Anyway I also removed this from etc nova nova conf on the compute nodes as we no longer have to route through the controller routing source ip x x x x For good measure etc init d nova compute restart etc init d nova network restart Finally I deleted my 192 168 0 0 24 on the controller and re created it nova manage network create fixed range v4 192 168 0 0 24 num networks 1 network size 256 multi host T label test The key above is specifying the multi host T This was more or less it Now when an instance is first started on a compute node the compute node itself gets an IP assigned from the network above and that IP gets assigned to the bridge br100 The instances on the host are then configured to use that IP as their gateway and traffic no longer gets routed through the controller One thing I noticed while working on this configuration was that my previous VPN connection didn t permit multiple clients As such I had to move my VPN server clients to use tls server and tls client which required a bit more work see this for more info My openvpn server file mode server tls server dev tap ifconfig 192 168 0 1 255 255 0 0 cert etc openvpn controller crt key etc openvpn controller key dh usr share doc openvpn examples easy rsa 2 0 keys dh1024 pem ca usr share doc openvpn examples easy rsa 2 0 keys ca crt daemon and openvpn client for compute1 tls client remote 10 176 65 54 dev tap cert etc openvpn compute1 crt key etc openvpn compute1 key ca etc openvpn ca crt daemon keepalive 10 60 up etc openvpn openvpn up up restart script security 2 The etc openvpn openvpn up file contains bin bash sbin ifconfig tap0 0 0 0 0 up usr sbin

    Original URL path: http://blog.defunct.ca/2011/09/19/using-nova-networks-multi_host-to-remove-spof/ (2015-04-05)
    Open archived version from archive


  • Moving nova-compute to a separate instance | boompty boomp
    ifconfig 192 168 0 1 255 255 255 0 secret etc openvpn openvpn key daemon EOF cat etc network if pre up d 00openvpn EOF bin bash usr sbin openvpn config etc openvpn openvpn server exit 0 EOF chmod 755 etc network if pre up d 00openvpn On nova compute cat etc openvpn openvpn client EOF remote 10 176 65 54 dev tap ifconfig 192 168 0 3 255 255 255 0 secret etc openvpn openvpn key daemon EOF cat etc network if pre up d 00openvpn EOF bin bash usr sbin openvpn config etc openvpn openvpn client usr sbin brctl addbr br100 usr sbin brctl addif br100 tap0 sbin ifconfig tap0 0 0 0 0 sbin ifconfig br100 192 168 0 3 exit 0 EOF chmod 755 etc network if pre up d 00openvpn Finally on both nodes echo flat interface tap0 etc nova nova conf This causes nova network to bridge into tap0 Let s recap what we ve done On nova cc we re configuring OpenVPN to act as a server We re bringing tap0 up with IP 192 168 0 1 24 and the etc network if pre up d 00openvpn script ensures that the VPN server is started on on boot specifically before the other network devices are brought up On nova compute we configure OpenVPN as a client and the etc network if pre up d 00openvpn script creates a bridge br100 adds the tap0 interface to it and then brings 192 168 0 3 up on br100 If I recall correctly the tap0 device doesn t appear to be up until we ifconfig it which is why we just set it to 0 0 0 0 Don t quote me on this though as I can t quite remember I know very little about bridging but essentially a bridge connects two or more different physical ethernets together to form one large logical ethernet taken from usr share doc bridge utils HOWTO and this is precisely what we have done here We bridge the virtual interfaces for running instances ie vnet0 with tap0 our VPN connection which means that nova cc can speak to instances running on nova compute and vice versa This is also essential as dnsmasq our DHCP server runs on nova cc spawned by nova network and without this bridging in place our instances would not be able to have their networking configured automatically on boot by the DHCP server Also the reason why we don t have to explicitly configure br100 on nova cc is because that runs nova network which handles the bridging automatically The only thing we did need to do on the nova cc side is instruct nova network on which device to bridge into flat interface tap0 The last thing I ll say here is that OpenVPN used device tun0 by default but we have to use tap0 a virtual Ethernet adapter as brctl creates Ethernet bridges and a tun device is a virtual point to

    Original URL path: http://blog.defunct.ca/2011/07/22/moving-nova-compute-to-a-separate-instance/ (2015-04-05)
    Open archived version from archive

  • Unable to console into Ubuntu 10.04 QEMU image | boompty boomp
    there I was able to console into the image This entry was posted in OpenStack Bookmark the permalink Programmatically interfacing with novaclient Using nova network s multi host to remove SPOF Leave a Reply Cancel reply You must be logged in to post a comment Search for Archives October 2013 March 2013 February 2013 May 2012 January 2012 September 2011 August 2011 July 2011 February 2011 June 2010 April 2010

    Original URL path: http://blog.defunct.ca/2011/09/18/unable-to-console-into-ubuntu-10-04-qemu-image/ (2015-04-05)
    Open archived version from archive



  • Programmatically interfacing with novaclient | boompty boomp
    Server 43 Server Server 44 Server Server 45 Server Server 46 for server in client servers list server delete client servers list This entry was posted in OpenStack Bookmark the permalink Running openstack dashboard Unable to console into Ubuntu 10 04 QEMU image Leave a Reply Cancel reply You must be logged in to post a comment Search for Archives October 2013 March 2013 February 2013 May 2012 January 2012

    Original URL path: http://blog.defunct.ca/2011/09/16/programmatically-interfacing-with-novaclient/ (2015-04-05)
    Open archived version from archive

  • Running openstack-dashboard | boompty boomp
    local settings py with correct values for NOVA DEFAULT ENDPOINT NOVA DEFAULT REGION NOVA ACCESS KEY NOVA SECRET KEY NOVA ADMIN USER NOVA PROJECT Most of these values can be ripped out of novarc on your cloud controller Continue on with the installation apt get install y python setuptools easy install virtualenv python tools install venv py tools with venv sh dashboard manage py syncdb When you run dashboard manage py syncdb it ll prompt you asking if you want to create a Django superuser since none exist at this point I answered yes entering a username that matched the value of NOVA ADMIN USER I initially tried creating a Django user with a different username and upon logging into openstack dashboard I failed to see my Nova project Lastly go ahead and start up the server tools with venv sh dashboard manage py runserver 0 0 0 0 8000 At this point you should be able to access your dashboard on http x x x x 8000 replacing x x x x with your openstack dashboard server s IP If you run into any issues refer to this which contains valid information for this particular version of the dashboard Again running with this old version of the dashboard isn t ideal and you certainly don t want to run it as root but hopefully this will point you in the right direction if you struggle to get the latest version to work with Nova My next task will to be to get a version of the dashboard and Nova which work together installed and operational This entry was posted in OpenStack Bookmark the permalink Moving nova compute to a separate instance Programmatically interfacing with novaclient Leave a Reply Cancel reply You must be logged in to post a comment

    Original URL path: http://blog.defunct.ca/2011/08/02/running-openstack-dashboard/ (2015-04-05)
    Open archived version from archive

  • October | 2013 | boompty boomp
    format json X GET H Authorization AWS access key hash of header and secret Continue reading Posted in Ceph Comments Off Search for Archives October 2013 March 2013 February 2013 May 2012 January 2012 September 2011 August 2011 July 2011 February 2011 June 2010 April 2010 March 2010 September 2009 August 2009 July 2009 May 2009 April 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008

    Original URL path: http://blog.defunct.ca/2013/10/ (2015-04-05)
    Open archived version from archive

  • March | 2013 | boompty boomp
    the exception of cloud images created through Continue reading Posted in OpenStack Comments Off Search for Archives October 2013 March 2013 February 2013 May 2012 January 2012 September 2011 August 2011 July 2011 February 2011 June 2010 April 2010 March 2010 September 2009 August 2009 July 2009 May 2009 April 2009 January 2009 December 2008 November 2008 October 2008 September 2008 August 2008 July 2008 June 2008 Categories Ceph Linux

    Original URL path: http://blog.defunct.ca/2013/03/ (2015-04-05)
    Open archived version from archive

  • February | 2013 | boompty boomp
    common rb 43 in rescue in block in deep const get can t get const Chef Node uninitialized constant Chef Node ArgumentError Continue reading Posted in Linux Tagged chef Comments Off Search for Archives October 2013 March 2013 February 2013 May 2012 January 2012 September 2011 August 2011 July 2011 February 2011 June 2010 April 2010 March 2010 September 2009 August 2009 July 2009 May 2009 April 2009 January 2009

    Original URL path: http://blog.defunct.ca/2013/02/ (2015-04-05)
    Open archived version from archive