Tag Info

New answers tagged

1

Our experimental ppa contains support for 'contributed' plugins to the installer. So far we have Heat, Ceilometer, Mongo, and a few others. Once we release 1.0 the plugins will be available in our stable repo. You can install the experimental packages to mess around with them: https://launchpad.net/~cloud-installer/+archive/ubuntu/experimental We'd love ...


1

You can customize the sizes of the VM's via a configuration file containing your services placements and their constraints. install_type: Single placements: controller: assignments: LXC: - nova-cloud-controller - glance - glance-simplestreams-sync - openstack-dashboard - juju-gui - keystone - mysql ...


0

The slightly older version of python-django in your output indicates that you may need to refresh your package lists. To make sure your packaging system is always working with current information, it is advisable to do this before package installations: sudo apt-get update -y


1

The official method is to use the Landscape OpenStack Autopilot. If not using the autopilot, the next recommended method is to use MAAS to commission the machines, then use Juju to deploy OpenStack. In these scenarios, MAAS handles DHCP for the broadcast domain behind your router ("LAN") and neutron handles DHCP for the instances in your tenant ...


0

The bleeding edge PPA's are hosted by the OpenStack Ubuntu testing team - the following are actively maintained: ppa:openstack-ubuntu-testing/icehouse ppa:openstack-ubuntu-testing/juno ppa:openstack-ubuntu-testing/kilo You can enable these using the add-apt-repository command: Example: sudo add-apt-repository ppa:openstack-ubuntu-testing/kilo Testing ...


1

The PPA should be ppa:cloud-installer/stable


3

The metadata commands you used will generate the index and other files. What seems to be the problem is a mismatch between the cloud/region name in those files, and what you have in your juju environments.yaml file. Could you compare them? Specifically the keystone (auth) url needs to match, byte for byte.


0

I re-ran the Landscape Autopilot step and the install completed successfully this time.


0

The guide you are referring to is for setting up a production or PoC instance. MAAS is only needed if you are going to provision multiple physical servers. For a single-node scenario, check out Adam's guide at http://astokes.org/ubuntu-openstack-installer/ for a very simple walkthrough of the installation.


0

It seems you have to sync-tools before you bootstrap. If you can sync during the bootstrap, there is not reason to do it after, as you are up to date (short of an update coming out). The problems I had were around not being able to sync-tools during bootstrap, because my cluster didn't have external access. My work around to do what IO alluded to in my ...


0

Never mind. You are clearly having problems before I was, and my answer won't help you. Your bootstrap machine does not have access to the internet, right? This is what worked for me. I named my environment maas, and my bootstrap machine jujuBS. I made a sub directory under my home called .juju to hold the tools and charms. I copied what I needed locally ...


5

I don't think it means you have to go to a website named maas.ip, but rather that you have to go to http://ww.xx.yy.zz where ww.xx.yy.zz is the IP address of the MAAS server.


0

It was a bios Issue, I have 4 NICs in each node and only two were connected. The timeout for the installer kicked in while the NIC's kept trying to PXE boot.


2

VNC connections can be a bit tricky to get going, but I have found the 'novnc' option works quite well: # Enable the 'novnc' juju set nova-cloud-controller 'console-access-protocol=novnc' juju debug-log # wait for some sort of quiet state Then, any new instances you launch should be able to get a console view in the web browser:


0

Perhaps this is what you found: https://insights.ubuntu.com/2015/01/15/virtualbox-extensions-for-maas/ More generally speaking, you'll need to set up your virtual networks with careful consideration for DHCP & DNS as mentioned in that post and in the MAAS docs.


4

By default, the Ubuntu distribution default will be installed when the charms are deployed. At the time of this post, it looks like this: trusty: Icehouse. utopic: Juno vivid: Kilo However, you can opt to use Juno or Kilo on trusty with the Cloud Archive. The charms have configuration options to allow you to change versions at deployment time. Be aware ...


0

There is no installation tutorial video, but comprehensive instructions are here: http://www.ubuntu.com/download/cloud/install-ubuntu-openstack You can see the installation process starting at 0:34 in this video https://www.youtube.com/watch?v=dCUoPmFGvCI It does not say that you need to install ubuntu on all machines because you don't: MAAS takes ...


1

Ok, I have done ceilometer deployment. After installing landscape openstack autopilot you need to do next things: From host where you have executed openstack-install: # If you used the install-openstack tool, you want to do this first: export JUJU_HOME=~/.cloud-install/juju juju status # Get an interactive shell with the right ENV sourced on the ...


1

Depends how long it has been stuck. These backtraces are normal during the deployment: it's trying to configure services that aren't ready yet, that's why it retries so many times. Juju is still deploying them, creating relations, etc. Depending on your hardware and network bandwidth, an autopilot run could take 40 minutes or even more. Has it given up ...


0

You are on your own here, since you are changing the environment that autopilot deployed. If you want, you can try following the charm readme: https://api.jujucharms.com/v4/trusty/ceilometer-3/archive/README.md But this is entirely unsupported. The next version of Landscape will deploy ceilometer.


4

To get access to the juju environment, please run the following from the place where you installed LDS: # If you used the install-openstack tool, you want to do this first: export JUJU_HOME=~/.cloud-install/juju juju status # Get an interactive shell with the right ENV sourced on the landscape # server itself. juju ssh landscape/0 sudo ...


2

You can run the following to attempt to restart the services: juju run --service landscape,landscape-msg 'sudo lsctl restart' For help on the root cause, I'll need to see more information, namely /var/log/juju/unit-landscape-0.log from landscape/0: # to get there: juju ssh landscape/0


1

I was having the same issue, so I ended up downloading all the "trusty-server-cloudimg-amd64" prefixed images. There was a tar which when unzipped contained a README.files that provided some information: This compressed tar archive contains files relevant to this machine image. Each filename is prefixed by a constant string denoting release and architecture ...


2

Landscape Managed, Scaleable Cloud See the following answer for the latest requirements: Installation Requirements for Landscape Autopilot TL;DR: 5 -- One machine for MAAS, one machine for Landscape, and three for your cloud. Single Machine There is a single machine option for getting a feel for things (using openstack-install), however it's not ...


6

These are the networking requirements for a successful OpenStack Autopilot run. Internet access MAAS and its nodes will need to be able to reach the internet, or at least these sites (http and https): maas.ubuntu.com cloud-images.ubuntu.com streams.canonical.com an Ubuntu archive (archive.ubuntu.com or a mirror) api.jujucharms.com manage.jujucharms.com ...


3

No, you shouldn't have to change the networking between the checklist and the configuration pages. Since you are using VMs, let's try something simple to begin with. First, make sure your VMs have enough RAM. The bootstrap node, that's the machine with 2 NICs, will need at least 4Gb, maybe 8Gb, since it will host all the administrative services like mysql, ...


2

For the OpenStack Autopilot in LDS 15.01, any 3 servers with IPMI will do, as long as they have 2 disks and at least one of them has 2 NICs (this isn't counting the LDS or MAAS machines, so 5 machines in total). In the most general sense, three servers that are Ubuntu certified will be enough, or if not certified, a BMC supported by MAAS is required (IPMI ...


0

Yes it will work with Private openstack as well but you'll want to call use OpenCloud\OpenStack; rather than use OpenCloud\Rackspace;


3

The "Missing N nova-compute units" message is about landscape-client agents registered back to landscape, Check /var/log/landscape/broker.log on the missing units. UPDATE: As you have correctly identified, things work smoothest if LDS (Landscape Dedicated Server) is installed to the same MAAS where your openstack will live, mostly because of network ...


1

You're trying to use the repository for Ubuntu 12.04 (precise). This is no longer supported. Change your repository to point to Ubuntu 14.04 (trusty) or Ubuntu 14.10 (utopic).


0

Ubuntu comes with a bare nova.conf and you are expected to add in all the other options. From the 1st link: You would need to add those sections (ie. [database], [glance], and [keystone_authtoken] sections.) , if the docs don't make it clear, please report it as a bug :) Packages should include at least the upstream example configuration ...


0

Try to set: no_proxy=10.16.37.215 this should help



Top 50 recent answers are included