Swift with Single server installation
Ronald Bradford
me at ronaldbradford.com
Wed Jun 3 12:44:13 UTC 2015
Thanks Adam. I was successfully able to add swift using experimental.
Ronald Bradford
Web Site: http://ronaldbradford.com
LinkedIn: http://www.linkedin.com/in/ronaldbradford
Twitter: @RonaldBradford
Skype: RonaldBradford
GTalk: Ronald.Bradford
IRC: rbradfor
On Tue, Jun 2, 2015 at 6:16 PM, Adam Stokes <adam.stokes at canonical.com> wrote:
> doh, right, sorry you'll need to run with the --extra-ppa cli option:
>
> sudo openstack-install --extra-ppa ppa:cloud-installer/experimental
>
>
>
> On Tue, Jun 2, 2015 at 6:10 PM, Ronald Bradford <me at ronaldbradford.com>
> wrote:
>>
>> Hi Adam,
>>
>> I had 0.22.3 installed from stable.
>>
>> NOTE: Be sure to remove running cloud -k and -u before updating software.
>>
>> I added experimental and removed stable repo.
>>
>> sudo apt-get update
>> sudo apt-get upgrade openstack
>>
>> This installed 0.99.12.
>>
>> When running I can confirm an updated interface (type first, password
>> second) and footer indicator of Kilo (new distro)
>>
>> It crashes with a reference to the wrong LXC container (the old name).
>> Is there a development branch you would like me to try to help
>> identify where this is?
>>
>>
>>
>> [DEBUG: 06-02 18:07:42, utils.py:738] Running command without waiting
>> for response.: sudo -H -u rbradfor TERM=xterm256-color ssh -t -q -l
>> ubuntu -o "StrictHostKeyChecking=no" -o "UserKnownHostsFile=/dev/null"
>> -i /home/rbradfor/.ssh/id_rsa 10.0.3.159 openstack-status
>> [ERROR • 06-02 18:07:43] • cloudinstall.utils • (utils.py, container_ip,
>> 579)]
>> error calling lxc-info to get container IP
>> Traceback (most recent call last):
>> File "/usr/share/openstack/cloudinstall/utils.py", line 571, in
>> container_ip
>> shell=True)
>> File "/usr/lib/python3.4/subprocess.py", line 616, in check_output
>> raise CalledProcessError(retcode, process.args, output=output)
>> subprocess.CalledProcessError: Command 'sudo lxc-info -n uoi-bootstrap
>> -i -H' returned non-zero exit status 1
>> [DEBUG • 06-02 18:07:43] • cloudinstall.utils • (utils.py,
>> global_exchandler, 63)]
>> Traceback (most recent call last):
>> File "/usr/share/openstack/cloudinstall/utils.py", line 571, in
>> container_ip
>> shell=True)
>> File "/usr/lib/python3.4/subprocess.py", line 616, in check_output
>> raise CalledProcessError(retcode, process.args, output=output)
>> subprocess.CalledProcessError: Command 'sudo lxc-info -n uoi-bootstrap
>> -i -H' returned non-zero exit status 1
>>
>> During handling of the above exception, another exception occurred:
>>
>> Traceback (most recent call last):
>> File "/usr/bin/openstack-status", line 94, in <module>
>> utils.container_run_status('uoi-bootstrap', 'openstack-status',
>> config)
>> File "/usr/share/openstack/cloudinstall/utils.py", line 634, in
>> container_run_status
>> ip = container_ip(name)
>> File "/usr/share/openstack/cloudinstall/utils.py", line 580, in
>> container_ip
>> raise NoContainerIPException()
>> cloudinstall.utils.NoContainerIPException
>>
>> Ronald Bradford
>>
>> Web Site: http://ronaldbradford.com
>> LinkedIn: http://www.linkedin.com/in/ronaldbradford
>> Twitter: @RonaldBradford
>> Skype: RonaldBradford
>> GTalk: Ronald.Bradford
>> IRC: rbradfor
>>
>>
>>
>> On Tue, Jun 2, 2015 at 3:59 PM, Adam Stokes <adam.stokes at canonical.com>
>> wrote:
>> > We've made several updates to the add service dialog in our experimental
>> > ppa,
>> >
>> > sudo apt-add-repository ppa:cloud-installer/experimental
>> >
>> > If you don't mind could you give that a try? We are getting pretty close
>> > to
>> > releasing a new version based off that codebase and I'd rather
>> > concentrate
>> > on fixing it there.
>> >
>> > Thanks
>> >
>> > On Tue, Jun 2, 2015 at 11:44 AM, Ronald Bradford <me at ronaldbradford.com>
>> > wrote:
>> >>
>> >> When attempting to add swift, with the (A)dd units option, I select
>> >> (X) swift-storage, use Number of units to add: 1 and select <OK>.
>> >>
>> >> The GUI provides the error.
>> >>
>> >> ERROR Exception in deploy watcher, re-trying.
>> >>
>> >> The $HOME/.cloud-install/commands.log file gives me.
>> >>
>> >> [DEBUG • 06-02 11:38:03] • cloudinstall.core • (core.py, add_charm,
>> >> 571)]
>> >> Add charm: swift-storage
>> >> [DEBUG • 06-02 11:38:03] • cloudinstall.charms • (__init__.py,
>> >> watch_deploy, 340)]
>> >> Starting charm deploy watcher.
>> >> [ERROR • 06-02 11:38:03] • cloudinstall.charms • (__init__.py,
>> >> watch_deploy, 350)]
>> >> Exception in deploy watcher, re-trying.
>> >> Traceback (most recent call last):
>> >> File "/usr/share/openstack/cloudinstall/charms/__init__.py", line
>> >> 344, in watch_deploy
>> >> err = charm.deploy() # TODO call with machine placement
>> >> TypeError: deploy() missing 1 required positional argument:
>> >> 'machine_spec'
>> >> [ERROR • 06-02 11:38:13] • cloudinstall.charms • (__init__.py,
>> >> watch_deploy, 350)]
>> >> Exception in deploy watcher, re-trying.
>> >> Traceback (most recent call last):
>> >> File "/usr/share/openstack/cloudinstall/charms/__init__.py", line
>> >> 344, in watch_deploy
>> >> err = charm.deploy() # TODO call with machine placement
>> >> TypeError: deploy() missing 1 required positional argument:
>> >> 'machine_spec'
>> >> [DEBUG • 06-02 11:38:23] • cloudinstall.charms • (__init__.py,
>> >> watch_relations, 359)]
>> >> Starting charm relations watcher.
>> >> [DEBUG • 06-02 11:38:23] • cloudinstall.charms • (__init__.py,
>> >> watch_post_proc, 378)]
>> >> Starting charm post processing watcher.
>> >>
>> >>
>> >> I have been able to use (A)dd units successfully to add (X)
>> >> nova-compute
>> >> units.
>> >>
>> >> For reference, selecting (X) ceph or (X) ceph-osd both produce the
>> >> same error as (X) swift-storage.
>> >>
>> >> Regards
>> >>
>> >> Ronald
>> >>
>> >>
>> >>
>> >> On Tue, Jun 2, 2015 at 10:04 AM, Ronald Bradford
>> >> <me at ronaldbradford.com>
>> >> wrote:
>> >> > Thanks Adam,
>> >> >
>> >> > That was a bit too obvious, surprised I did not see it reading the
>> >> > docs.
>> >> > Will try it out.
>> >> >
>> >> > Regards
>> >> >
>> >> > Ronald
>> >> > Ronald Bradford
>> >> >
>> >> > Web Site: http://ronaldbradford.com
>> >> > LinkedIn: http://www.linkedin.com/in/ronaldbradford
>> >> > Twitter: @RonaldBradford
>> >> > Skype: RonaldBradford
>> >> > GTalk: Ronald.Bradford
>> >> > IRC: rbradfor
>> >> >
>> >> >
>> >> >
>> >> > On Tue, Jun 2, 2015 at 9:38 AM, Adam Stokes
>> >> > <adam.stokes at canonical.com>
>> >> > wrote:
>> >> >> If you hit the 'A' key while in the status screen it'll bring up a
>> >> >> dialog
>> >> >> which would allow you to add additional swift storage/proxy
>> >> >>
>> >> >> On Tue, Jun 2, 2015 at 9:35 AM, Ronald Bradford
>> >> >> <me at ronaldbradford.com>
>> >> >> wrote:
>> >> >>>
>> >> >>> Hi,
>> >> >>>
>> >> >>> I wanted to know if there was a way to get a working swift storage
>> >> >>> environment with the Single Server installer.
>> >> >>> While the installer makes reference to an option --storage
>> >> >>> {ceph,swift} Choose storage backend to deploy initially, and a
>> >> >>> subsequent note, it is not clear via your documentation if it is
>> >> >>> possible.
>> >> >>>
>> >> >>> Adding this option does not appear to have any effect.
>> >> >>>
>> >> >>> Is there a recommended Juju way to add this to an existing
>> >> >>> deployment?
>> >> >>>
>> >> >>> Thanks
>> >> >>>
>> >> >>>
>> >> >>> Regards
>> >> >>>
>> >> >>> Ronald
>> >> >>>
>> >> >>> Ronald Bradford
>> >> >>>
>> >> >>> Web Site: http://ronaldbradford.com
>> >> >>> LinkedIn: http://www.linkedin.com/in/ronaldbradford
>> >> >>> Twitter: @RonaldBradford
>> >> >>> Skype: RonaldBradford
>> >> >>> GTalk: Ronald.Bradford
>> >> >>> IRC: rbradfor
>> >> >>>
>> >> >>> --
>> >> >>> 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
>> >> >>
>> >> >>
>> >
>> >
>
>
More information about the ubuntu-openstack-installer
mailing list