Single Installer problems

Thu Jun 11 14:32:32 UTC 2015

On Thu, Jun 11, 2015 at 9:57 AM, Vatkov, Bogdan <bogdan.vatkov at sap.com>
wrote:

>  I do not have issues with resources on the box (have 32 cores and 256 GB
> RAM), so I could run many instances.
>
>
>
> Right after install I was not able to create instances due to the
> following error in  /var/log/nova/nova-compute.log I had the error:
>
> libvirtError: internal error: no supported architecture for os type 'hvm'.
>
>
>
> When I tried sudo kvm-ok it said:
>
> INFO: Your CPU does not support KVM extensions
>
> KVM acceleration can NOT be used
>
>
>
> So, KVM virtualization nesting is for whatever reason not possible...
>
>
>
> Changing virt-type to qemu in Juju did nothing, and yes I did commit, so I
> had to manually change virt_type=kvm to virt_type=qemu in
> /etc/nova/nova-compute.conf.
>
> After this change I am able to create VMs.
>

You can create a `charmconf.yaml` to pass into the installer to change the
default virt_type for nova-compute, have a look at
~/.cloud-install/charmconf.yaml for examples.

>
>
> My next problem is that I cannot make Neutron networks run as expected,
> tried all sorts of internal/external networks combinations to no success.
> It could be that I am missing something very simple but I can’t see it.
>
> Right after instance creation the instance log claims IP is successfully
> reserved, yet I cannot do ssh to that IP nor can I even ping it. I do not
> see any errors in the Neutron log and have no idea where to start
> debugging.
>
> Any idea? Which artifacts do you need? Log? Some commands to run?
>

I haven't added it to the official docs yet but another user graciously
provided some steps for configuring neutron seen at this bug:
https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues/616

>
>
> Thanks in advance!
>
>
>
> *From:* Adam Stokes [mailto:adam.stokes at canonical.com]
> *Sent:* Monday, June 08, 2015 17:09
>
> *To:* Vatkov, Bogdan
> *Cc:* Sacha Yunusic; Ronald Bradford; ubuntu-openstack-installer
> *Subject:* Re: Single Installer problems
>
>
>
> You should be able to at least run a single instance in nova with the
> single installer. If you need more flexibility you'll want to use MAAS plus
> a mix of bare metal/KVM's (or all KVMS).
>
>
>
> Can you also file a bug on the apt-add-repository not respecting the proxy
> configuration?
> https://github.com/Ubuntu-Solutions-Engineering/openstack-installer/issues
>
>
>
> On Mon, Jun 8, 2015 at 9:51 AM, Vatkov, Bogdan <bogdan.vatkov at sap.com>
> wrote:
>
>  Yes, as outlined in my initial post – I am behind a proxy and I am
> always using the -http-proxy and --https-proxy parameters and as I said
> earlier – they did work… but only to a certain extent – the
> add-apt-repository command was for whatever reason not respecting them.
>
> That is why I had to change the code of the openstack-installer (the
> userdata.yaml template).
>
> I would be happy to see a more elegant fix but the template fix at least
> works for me right now – I have managed to install all of the default
> openstack services and now the installer waits in “Validating network
> parameters for Neutron…” already an hour now in that state…
>
> At least the Horizon is up and running, even Juju GUI works (installed it
> explicitly from within the installer GUI).
>
> Cannot make Nova run yet as it seems only 1 VCPU and 1 GB RAM were
> assigned to the hypervisor on “ubuntu-local-machine-2”.
>
>
>
>
>
> *From:* Adam Stokes [mailto:adam.stokes at canonical.com]
> *Sent:* Monday, June 08, 2015 15:42
> *To:* Vatkov, Bogdan
> *Cc:* Sacha Yunusic; Ronald Bradford; ubuntu-openstack-installer
>
>
> *Subject:* Re: Single Installer problems
>
>
>
> Make sure you are running the installer with:
>
>
>
> --http-proxy and --https-proxy as that should populate all the necessary
> proxy information.
>
>
>
> On Mon, Jun 8, 2015 at 7:57 AM, Vatkov, Bogdan <bogdan.vatkov at sap.com>
> wrote:
>
>  Ok, I have managed to go past the container initialization by changing
> the template at: /usr/share/openstack/templates/userdata.yaml…
>
>
>
> changing  from:
>
> - source: deb http://ppa.launchpad.net/cloud-installer/testing/ubuntu
> $RELEASE main
>
> to:
>
> - source: deb http://ppa.launchpad.net/cloud-installer/experimental/ubuntu
> $RELEASE main
>
>
>
>
>
> @Sacha, have you managed to complete the install?
>
>
>
> Best regards,
>
> Bogdan
>
>
>
> *From:* Sacha Yunusic [mailto:sacha at penta-sec.com]
> *Sent:* Monday, June 08, 2015 14:07
> *To:* Vatkov, Bogdan; Adam Stokes; Ronald Bradford
> *Cc:* ubuntu-openstack-installer
>
>
> *Subject:* RE: Single Installer problems
>
>
>
> When I tried to use proxy on the installation I had the same problem. For
> some commands were used proxy and for some other, not.
>
>
>
> Sacha
>
>
>
> Sent from my Samsung device
>
>
>
> -------- Original message --------
> From: "Vatkov, Bogdan" <bogdan.vatkov at sap.com>
> Date: 08/06/2015 06:10 (GMT-03:00)
> To: Adam Stokes <adam.stokes at canonical.com>, Ronald Bradford <
> me at ronaldbradford.com>
> Cc: ubuntu-openstack-installer <
> ubuntu-openstack-installer at lists.ubuntu.com>
> Subject: RE: Single Installer problems
>
> Hi Adam,
>
>
>
> As I mentioned in my initial post “I had to upgrade the kernel to
> 3.16-0-38.52 based on this:
> https://bugs.launchpad.net/uvtool/+bug/1408833”.
>
> So this one is ok. My main problem for now seems to be proxy settings not
> being properly propagated to all commands the installer is launching,
> add-apt-repository is one – see details in my other post from 2 minutes ago.
>
> Any hints on how this could be fixed are welcome!
>
>
>
> Thanks in advance!
>
>
>
> Best regards,
>
> Bogdan
>
>
>
>
>
> *From:* Adam Stokes [mailto:adam.stokes at canonical.com
> <adam.stokes at canonical.com>]
> *Sent:* Sunday, June 07, 2015 19:22
> *To:* Ronald Bradford
> *Cc:* Vatkov, Bogdan; ubuntu-openstack-installer
> *Subject:* Re: Single Installer problems
>
>
>
> Also if you've installed a fresh 14.04.2 on your host server there are
> some kernel issues wrt apparmor. Make sure you've `apt-get dist-upgrade`
> before performing the single install. You want to be at a kernel higher
> than 3.16.0-30
>
>
>
> On Sat, Jun 6, 2015 at 3:14 PM, Ronald Bradford <me at ronaldbradford.com>
> wrote:
>
>  For me the following works.
>
>
>
> $ sudo openstack-install --extra-ppa ppa:cloud-installer/experimental
>
>
>
> Can you try that without the additional arguments you have.
>
>
>
>
>
> I received an error running:
>
>
>
> $ sudo openstack-install --extra-ppa ppa:cloud-installer/experimental
> --openstack-release kilo -r trusty -a amd64
>
>
>
> I ran without -r trusty, got an error.
>
>
>
> I ran without -a amd64, got an error.
>
>
>
> I ran without -r trusty and -a amd64, got an error.
>
>
>
> I removed --openstack-release kilo and it worked.  This seems the issue. kilo
> is the default release.
>
>
>
> This works.
>
>
>
> $ sudo openstack-install --extra-ppa ppa:cloud-installer/experimental -r
> trusty -a amd64
>
>
>
>
>
> Ronald
>
>
>       Ronald Bradford
>
>
>
> Web Site: http://ronaldbradford.com
> LinkedIn:  http://www.linkedin.com/in/ronaldbradford
> Twitter:    @RonaldBradford <http://twitter.com/ronaldbradford>
> Skype:     RonaldBradford
>
> GTalk:     Ronald.Bradford
>
> IRC:         rbradfor
>
>
>
> On Sat, Jun 6, 2015 at 1:53 PM, Ronald Bradford <me at ronaldbradford.com>
> wrote:
>
>  I went threw this process this week without any issues.
>
>
>
> Here are the steps I used --
> http://ronaldbradford.com/blog/deploying-ubuntu-openstack-kilo-2015-06-06/
>
>
>
> Ronald
>
>
>       Ronald Bradford
>
>
>
> Web Site: http://ronaldbradford.com
> LinkedIn:  http://www.linkedin.com/in/ronaldbradford
> Twitter:    @RonaldBradford <http://twitter.com/ronaldbradford>
> Skype:     RonaldBradford
>
> GTalk:     Ronald.Bradford
>
> IRC:         rbradfor
>
>
>
> On Fri, Jun 5, 2015 at 7:52 PM, Vatkov, Bogdan <bogdan.vatkov at sap.com>
> wrote:
>
>  I also see (in the cloud-init.log) that the proxy settings are
> propagated to the environment and also to the apt config in particular:
>
> …
>
> Jun  5 18:53:02 openstack-single-ubuntu [CLOUDINIT] util.py[DEBUG]:
> Writing to /etc/apt/apt.conf.d/95cloud-init-proxy - wb: [420] 113 bytes
>
> …
>
> But this conf would only affect the apt but not the add-apt-repository
> command, which I could so far make run behind proxy by:
>
> 1)      Exporting the http_proxy as some user and then
>
> 2)      sudo –E add-apt-repository ….
>
> But I have no idea how to make this work in the cloud-init story ….any
> idea how can I hack this one?
>
>
>
>
>
>
> --
> ubuntu-openstack-installer mailing list
> ubuntu-openstack-installer at lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-openstack-installer
>
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-openstack-installer/attachments/20150611/5eed89c8/attachment-0001.html>