New answers tagged openstack
I'm going to append a slight bundle modification below that should get you up and running. sample: services: ubuntu: charm: "cs:trusty/ubuntu" num_units: 1 mysql: to: lxc:ubuntu=0 charm: "cs:precise/mysql-27" num_units: 1 annotations: "gui-x": "139" "gui-y": "168" wordpress: to : ...
I've seen anecdotal evidence on the juju mailing list that using juju from the juju stable ppa resolved this issue for at least one person. Here's the mailing list post
This is being handled as a bug report: https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/374?
I had a similar error. Not exactly the same, but the solution was to remove the lxcs. rm -rf /var/lib/lxc/offending-container-xx rm -rf /var/lib/juju/containers/offending-container-xx If someone comes across a similar error, hopefully this will help.
OK the only thing that worked for me is commenting "driver = keystone.token.persistence.backends.sql.Token" of the [token] section in the /etc/keystone/keystone.conf file
My current solution is: find out the IP schema for internal IPs (in my case: 10.115.x.x) and create corresponding rule in the ssh config: Host 10.115.* ProxyCommand ssh forward@my_gateway_machine nc -q0 %h %p
I don't have an answer for your current problem with devstack but invite you to try out our OpenStack Installer: http://ubuntu-cloud-installer.readthedocs.org/en/latest/ Single install mode is useful for running a test OpenStack cloud on a laptop or single machine. Multi makes use of MAAS and Landscape Autopilot will set you up using a reference ...
You'll want to select the Multi Install path in order to place your services on your existing seven machines. It should work fine with single disks on each machine. This link should get you started with the installer, juju, and maas. http://ubuntu-cloud-installer.readthedocs.org/en/latest/multi-installer.guide.html
The Beta of the OpenStack Autopilot can deploy on up to 10 physical nodes before running into the limits of its built-in license. To be clear, the 10 free nodes will continue to be available even after the Beta period ends. Finally, the current Beta does not support HA yet.
I believe you're running into this issue, KVM doesn't work inside virtualbox: How to enable nested virtualization in ubuntu Bug report with Virtualbox: https://www.virtualbox.org/ticket/4032
There is a license restriction, Landscape managed machines (real, or virtual) require licenses. A managed machine is one on which the landscape-client is installed, and registered with the server. So long as you don't register any other machines in it, Landscape Dedicated Server ships now with enough free licenses to build a simple cloud utilising 10 ...
Have you tried to make sure you use the proper accelaration for qemu? Such as: qemu-system-x86_64 -machine accel=kvm [...] This switch could make your computer use hardware virtualization (cpu usage drops to negligible then)
Try Juju: Configuring for Amazon Web Services
What's failing is the juju bootstrap step. You should try that outside of the cloud installer to see if you can get more information. Point juju at your MAAS environment and try to bootstrap there. If a plain juju bootstrap doesn't yield any clues, try juju bootstrap --debug. Also make sure that you have nodes in the ready state in MAAS.
Top 50 recent answers are included