Openstack Ubuntu 16.04 MAAS 2.x conjure cloud install part 2

7 thoughts on “Openstack Ubuntu 16.04 MAAS 2.x conjure cloud install part 2”

• Chris, working on setting up openstack for a capstone project.  We have run into some issues with the deployment of our nodes.  We have looked at your website and can't find any documentation on Deploying nodes.  If you have any way to point us it would be much appreciated.  We are using one Bare metal server that contains MAAS. 5virtual machines, one acting as a juju controller the others as regular nodes.  We have a private network 192.x.x.x and a network that reaches out to the internet 172.x.x.x  ANY HELP WOULD BE APPRECIATED.

• Hi Chris,

  I have setup Ubuntu Cloud using MAAS.

  My MAAS internal N/W for PXE is 10.1.1.0/24
  My Cloud VM's admin network is 10.10.0.0/24
  Compute nodes are running on 10.1.1.0/24 and VM's are running on 10.10.0.0/24

  How to connect compute ( 10.1.1.0/24 ) to VM's N/W ( 10.10.0.0 / 24 ) ?
  Since there is no physical NIC involved for 10.10.0.0/24 , I may not be able to route t he packets from 10.1.1.0/24 to 10.10.0.0/24.

  Any idea on this ?

  Thanks.

• Great video! However, can't you only use a limited amount of machines using on-premises landscape in the event you want to scale? Can you just use Juju and it's UI to do the same thing without the Landscape limitations?

• Could you show how the interfaces were configured on the N additional nodes that you added between video 1 and 2. When I get to this stage, sometimes Landscape complains that "at least one node with two or more interfaces..", this despite that I have +2 nodes with multiple nics. On the otherhand, sometimes its passes that without a problem.. But then OpenVSwitch has no public network in the dropdown.. Tried the irc channels but no joy….

• This has been awesome in getting my development lab up and running. I've got the system upand running and just got the internal juju-gui up and running. The one thing I'd like to figure out how to do is setup networking so that the external network exits via a vlan instead of the physical interface, for example VLAN 50. I've seen lots of stuff how to do it with things like packstack. But the problem with this install is that it doesn't do things the 'normal' way that it shows on openstack.org For example there is no ml2_config.ini on any of the nodes eventhough I know it uses ml2.

  I setup my vlans in the subnet section in MAAS and have them all set on the eth1 of all my nodes where the physical is left unconfigured and the 4 sub interfaces have vlans and subnets configured (with IP unconfigured). All the documentation (again non autopilot) I've seen says that you should create a bridge called 'br-vlan' (to access the vlan driver) to ovs and attach the physical interface that will use the vlans. However this is attached to br-data.

• chris, once again thanks for video.
  Here, after selecting the hardware and running autopilot, in my case, the "bootstrap juju controller" stage is stuck at 4%. Since, it won't automatically power on the server, I powered the deploying server using etherwake from background. However, even after deployment completed, the progress is still stuck at 4%. Also, I tried logging into the deployed node using ubuntu@ip-address. This also failed informing that "Permission denied (publickey)." Have you faced any similar issues? anything that you suggest here? Thanks for the help in advance.

• thanks

Comments are closed.