openstack team mailing list archive

[Sebastian Stadil <sebastian@xxxxxxxxx>]

Thanks for using email. Works much better, at least for me.

Scalr built a light-weight guest agent in python that we could perhaps use
for this use case. It collects and reports data (from the OS and
application), but is also in charge of executing scripts on defined events
(before a reboot, after the IP address changed, etc), and sometimes changing
local configuration files (like httpd.conf, my.cnf, or nginx.conf). It
wouldn't be too hard to add what you are talking about.

Source code is still at http://code.google.com/p/scalr/, Mike (Mayo) and I
have yet to create a project for it on launchpad.

On Tue, Dec 14, 2010 at 9:36 PM, Ed Leafe <ed.leafe@xxxxxxxxxxxxx> wrote:

> [re-posted to the correct list]
>
>        I’m working on the blueprint for resetting the admin password on a
> XenServer instance (
> https://blueprints.launchpad.net/nova/+spec/xs-password-reset), but I
> wanted to run this by the community to get some feedback/input on the
> design, since it is potentially applicable to other use cases in OpenStack.
> I figured that email would be a better choice than IRC because of time
> zones, work schedules, etc.
>
>        Please keep in mind that the entire concept of a guest agent and
> communication between it and the host will be completely *optional*. At
> Rackspace, since we actively manage guest instances for our customers, it
> makes a lot of sense. For other applications there would be no need at all
> for this, and lots of reasons not to. Another aspect is that this is
> intended for communicating with running instances, not for the initial
> creation. What I'm looking for are other potential use cases for when
> someone would need the host to communicate to the guest and vice-versa.
>
>        The current design uses a guest agent installed on the instance that
> regularly checks XenStore for password reset requests. Obviously this is a
> XenServer-specific design, so I’m looking for suggestions on a
> hypervisor-agnostic solution for the request store: one that is as
> lightweight as possible, and which hosts and guests would be able to access.
>
>        When the guest agent finds a password reset request in the store, it
> starts the password resetting routines, and updates the record with its
> status, which the host can check to report back to the requester. I think
> that this approach is simple enough to work for any agent requests, not just
> password resetting, but I’d like to hear other ideas if you have any.
>
>
> -- Ed Leafe
>
> Confidentiality Notice: This e-mail message (including any attached or
> embedded documents) is intended for the exclusive and confidential use of
> the
> individual or entity to which this message is addressed, and unless
> otherwise
> expressly indicated, is confidential and privileged information of
> Rackspace.
> Any dissemination, distribution or copying of the enclosed material is
> prohibited.
> If you receive this transmission in error, please notify us immediately by
> e-mail
> at abuse@xxxxxxxxxxxxx, and delete the original message.
> Your cooperation is appreciated.
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>