New answers tagged

0

Elaborating on @Rinzwind's comment: pip is a manager for python packages. You need the python 2.7 version of pip, which can be installed like this sudo apt-get install python-pip Take a look at the pip documentation for installation details and alternative installation options. I would recommend using a distribution like anaconda to manage your python ...


6

Try this. I have used the "next" PPA of conjure-up because it has a lot of fixes, but it also uses Juju 2.0 beta which is a beta :) Your call on whether you do that or use stock conjure-up from the stable archives. Note that the main archive will be updated to get the new conjure-up anyway, once Juju 2.0 is released. If you are going to build your cloud on ...


0

The packages and dependencies needed for OpenStack are in the Canonical Cloud Archive, which is not the archie you have installed. See https://wiki.ubuntu.com/ServerTeam/CloudArchive for details. You can use those packages together with puppet or chef or your preferred configuraiton management system to build whatever kind of openstack you like. However, ...


3

The main problem is that the virtual disk you have created is not formatted, it is just a raw disk without a partition table. Another issue is that you selected the format qcow2 and created an .img file. You have to execute this command : qemu-img create -f qcow2 ubuntu.qcow2 20G. Download the latest stable version of GParted Live | Direct download link ->...


0

EDIT: I was able to get to the rpi_3_config part, but the next command gave an error. EDIT #2: I am now able to compile u-boot successfully from the official u-boot git repo EDIT #3: So far it looks successful with it's booting. Can't test it right now, but I will try with MaaS later! While you might not be able to PXE boot a Raspberry Pi 3 without an SD ...


0

MAAS should be using Ubuntu 14.04 to commission. Can you try to update MAAS and see if that solves the problem?


0

Here is the solution: sudo apt install conjure-up conjure-up openstack


0

This screen gives you an overview of what services will be deployed. This is changing in the next release of conjure-up to be more tutorial like and less overwhelming. For now just tabbing over to commit will accept all the defaults and give you a fully deployed OpenStack.


1

The hardware I have 3rd generation Intel NUC with i7, 16G RAM, 250 SSD and a 300mbps connection. Picking the OpenStack with NovaLXD option so everything is deployed on a single system takes me about 30 minutes for a full deployment. This includes importing glance images, configuring keystone, configuring neutron and starting a compute instance to verify ...


1

It looks like your user isn't part of the LXD group. Add your user to the LXD group: sudo usermod -a -G lxd username ...replacing username with your username.


1

After reproduce this problem myself using JuJu/MAAS, I found out MAAS deployment install quite a few packages: Installing package: curl Installing package: cpu-checker Installing package: bridge-utils Installing package: rsyslog-gnutls Installing package: cloud-utils Installing package: cloud-image-utils Installing package: tmux Some of the packages ...


0

Messing up with permissions like that won't get you anywhere.. If you don't want to use the tested 14.04 lts, perhaps you can use docker, and simply follow the official procedure as described here..


0

I suppose you could do either. However, depending on the size of your intended cloud, running MAAS separately from where you run openstack-install might make sense. Most deployments I would expect you to run openstack-install on your MAAS server, infact, the instructions intend on you doing exactly that. The first step of the installer is to install ...


0

Answer taken from UbuntuForums.org Openstack single node install - Xenial? verbatim: sudo apt-add-repository ppa:cloud-installer/stable sudo apt-get update sudo apt-get install openstack sudo openstack-install I've not yet tested this myself, but expect to in a day or so. Yes, it is a single node install. For a more authoritative build with heavier ...


2

There is no package named 'xenial/proposed', however there is a repository called that name. Note: enabling the repository xenial/proposed is not really encuraged because it contains bleeding edge developtment packages which may even be able to break your setup To easily enable all the repositories you can change your /etc/apt/sources.list by: sudo nano /...


3

While you may not be able to PXE boot via MAAS on the RPi3, juju supports manual provisioning including the bootstrap node - https://jujucharms.com/docs/1.24/config-manual With this you can install the systems with 16.04, then allow juju to provision them into the environment via SSH.


0

I could imagine a number of things going wrong but I suspect you may have defined an apt proxy in maas and perhaps formatted it like 'ip:port' instead of 'http://ip:port' Just a guess. That setting is in the MAAS UI, in the settings area.


1

Have you tried changing your Gateway IP on your MAAS set up? If the route to your outfacing NIC is not resolving, this could also be an IP forwarding issue. You might wanna check to see your firewall is not an issue here in case the traffic is blocked (though you can telnet to it).


0

I figured I would answer this having more knowledge in CEPH then when I asked the question. Although, I can't say why the defaults are the defaults in Horizon. If they are generated or just a starting place for openstack. Landscape drive usage is pulled from ceph, which already includes replication. cluster eabab000-231c-4edb-855c-dd30b1bab56d ...


0

Try to configure lxdbr0 by dpkg-reconfigure -p medium lxd Maybe it's because lxdbr0 is not configured yet. Let me know if it works for you.


0

berryboot will let you do network booting but its not real PXE http://www.berryterminal.com/doku.php/berryboot


3

I'll try to provide a starting answer, and hopefully someone can edit and improve my answer if they have more relevant information. Configuration options can be found at JUJU Keystone Charm. From your machine with juju tools installed. export JUJU_HOME=~/.cloud-install/juju juju ssh landscape-server/0 sudo 'JUJU_HOME=/var/lib/landscape/juju-homes/`sudo ls ...



Top 50 recent answers are included