Login | Register For Free | Help
Search for: (Advanced)

Mailing List Archive: OpenStack: Operators

Re: [Openstack] Health & Monitoring Blueprints

 

 

OpenStack operators RSS feed   Index | Next | Previous | View Threaded


duncan at dreamhost

Apr 11, 2012, 1:43 PM

Post #1 of 12 (479 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints

Resharing with the Operators list...

d

On Wed, Apr 11, 2012 at 4:33 PM, Wilkinson, Lyle <lyle.wilkinson [at] hp> wrote:
> Hi folks,
>
>
>
> We’ve created a set of 3 blueprints on the topics of health and monitoring,
> metrics data collection, and cloud inventory maintenance.
>
>
>
> https://blueprints.launchpad.net/nova/+spec/resource-monitor-alerts-and-notifications
>
> https://blueprints.launchpad.net/nova/+spec/utilizationdata
>
> https://blueprints.launchpad.net/nova/+spec/cloud-inventory-manager
>
>
>
> We’re hoping to discuss these at the design summit next week, but currently
> don’t know if they’ll be part of an existing session or covered in a
> separate session in one of the open space.  We’ve created some etherpad
> pages to get the discussion going, so if you have questions, suggestions,
> etc., feel free to contribute there.
>
>
>
> http://etherpad.openstack.org/ResourceMonitorAlertsandNotifications
>
> http://etherpad.openstack.org/utilizationdata
>
> http://etherpad.openstack.org/Cloud-Inventory-Manager
>
>
>
> Thanks in advance!
>
>
>
> Lyle Wilkinson
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack [at] lists
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
>
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


matt at nycresistor

Apr 11, 2012, 2:03 PM

Post #2 of 12 (462 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

Problem of course is many operators aren't on the design summit
contributor list ( ala don't have codes to get into it ) and if it's
later it's 500 USD to attend.

Maybe not the best means of collaborating on something that effects them deeply.

Pondering that.

-Matt

On Wed, Apr 11, 2012 at 1:43 PM, Duncan McGreggor <duncan [at] dreamhost> wrote:
> Resharing with the Operators list...
>
> d
>
> On Wed, Apr 11, 2012 at 4:33 PM, Wilkinson, Lyle <lyle.wilkinson [at] hp> wrote:
>> Hi folks,
>>
>>
>>
>> We’ve created a set of 3 blueprints on the topics of health and monitoring,
>> metrics data collection, and cloud inventory maintenance.
>>
>>
>>
>> https://blueprints.launchpad.net/nova/+spec/resource-monitor-alerts-and-notifications
>>
>> https://blueprints.launchpad.net/nova/+spec/utilizationdata
>>
>> https://blueprints.launchpad.net/nova/+spec/cloud-inventory-manager
>>
>>
>>
>> We’re hoping to discuss these at the design summit next week, but currently
>> don’t know if they’ll be part of an existing session or covered in a
>> separate session in one of the open space.  We’ve created some etherpad
>> pages to get the discussion going, so if you have questions, suggestions,
>> etc., feel free to contribute there.
>>
>>
>>
>> http://etherpad.openstack.org/ResourceMonitorAlertsandNotifications
>>
>> http://etherpad.openstack.org/utilizationdata
>>
>> http://etherpad.openstack.org/Cloud-Inventory-Manager
>>
>>
>>
>> Thanks in advance!
>>
>>
>>
>> Lyle Wilkinson
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack [at] lists
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
> _______________________________________________
> Openstack-operators mailing list
> Openstack-operators [at] lists
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


duncan at dreamhost

Apr 11, 2012, 2:16 PM

Post #3 of 12 (460 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

On Wed, Apr 11, 2012 at 5:03 PM, Matt Joyce <matt [at] nycresistor> wrote:
> Problem of course is many operators aren't on the design summit
> contributor list ( ala don't have codes to get into it ) and if it's
> later it's 500 USD to attend.
>
> Maybe not the best means of collaborating on something that effects them deeply.
>
> Pondering that.

That's a really good point. In the post-conference conversations that
deal with attendance policy, this should be kept in mind.

In lieu of not being able to attend in person, keep in mind the
live-casting that will be done, in combination with IRC channels. When
I led tracks at Ubuntu Developer Summits, we were able to keep remote
attendees closely in the loop. As non-optimal as this may be, we can
still work hard to get the best out of it.

I'm not sure it the Design Summit will be projecting IRC chat on a
screen for each session (like is done at UDS); at the very least, I
can make sure I'm on Freenode and can act as a proxy -- ensuring any
questions or concerns from IRC get audibly voiced and become part of
the conversation. I will be attending all of the DevOps (and related)
sessions, as long as they don't conflict.

Thanks for bringing this up,

d
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


stefano at openstack

Apr 11, 2012, 2:52 PM

Post #4 of 12 (462 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

On Wed, 2012-04-11 at 14:03 -0700, Matt Joyce wrote:
> Problem of course is many operators aren't on the design summit
> contributor list ( ala don't have codes to get into it ) and if it's
> later it's 500 USD to attend.

There will be over 400 people at the summit, not all of them are
developers. I expect lots of operators/users have a representation
there. Will there be enough to justify having this discussion there? I
don't know but we can try.

On Wed, 2012-04-11 at 17:16 -0400, Duncan McGreggor wrote:
> That's a really good point. In the post-conference conversations that
> deal with attendance policy, this should be kept in mind.

We probably should set a date for a post-mortem discussion, after the
conference. I'm quite sure I'll take a few days off after April 20,
maybe have a couple of live feedback sessions in the first week of May
would work?

> In lieu of not being able to attend in person, keep in mind the
> live-casting that will be done,


We're not yet sure to be able to offer this. Wait for an official
communication.

> in combination with IRC channels.

This we can do: use IRC but there will be only one projector in the
rooms, not two like at UDS. Each track leader can decide how to use it
(for IRC or something else).

Since you are already familiar with UDS setup, would you mind setting up
the IRC channels for each of the rooms at the summit? This is the layout
of the rooms and their expected usage:

Ballroom: Intro Plenary, Breakout tables, Lightning Talks

Seacliff A+B: Design summit sessions (fishbowl setup)*
Seacliff C: Design summit sessions (fishbowl setup)*
Seacliff D: Design summit sessions (fishbowl setup)*
Marina: Design summit sessions (fishbowl setup)*
Bayview B: Design summit sessions (fishbowl setup)*

Golden Gate: Unconference room (theater setup)*
Bayview A: Developer's lounge

The association between rooms+track will be published soon, once the
revisions on summit.openstack.org are completed.

Cheers,
stef

_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


duncan at dreamhost

Apr 11, 2012, 3:00 PM

Post #5 of 12 (462 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

On Wed, Apr 11, 2012 at 5:52 PM, Stefano Maffulli <stefano [at] openstack> wrote:
> On Wed, 2012-04-11 at 14:03 -0700, Matt Joyce wrote:
>> Problem of course is many operators aren't on the design summit
>> contributor list ( ala don't have codes to get into it ) and if it's
>> later it's 500 USD to attend.
>
> There will be over 400 people at the summit, not all of them are
> developers. I expect lots of operators/users have a representation
> there. Will there be enough to justify having this discussion there? I
> don't know but we can try.
>
> On Wed, 2012-04-11 at 17:16 -0400, Duncan McGreggor wrote:
>> That's a really good point. In the post-conference conversations that
>> deal with attendance policy, this should be kept in mind.
>
> We probably should set a date for a post-mortem discussion, after the
> conference. I'm quite sure I'll take a few days off after April 20,
> maybe have a couple of live feedback sessions in the first week of May
> would work?

+1 for me!

>> In lieu of not being able to attend in person, keep in mind the
>> live-casting that will be done,
>
> We're not yet sure to be able to offer this. Wait for an official
> communication.

Whoops, my bad -- sorry about that Stefano!

>> in combination with IRC channels.
>
> This we can do: use IRC but there will be only one projector in the
> rooms, not two like at UDS. Each track leader can decide how to use it
> (for IRC or something else).
>
> Since you are already familiar with UDS setup, would you mind setting up
> the IRC channels for each of the rooms at the summit?

Sure thing!

> This is the layout
> of the rooms and their expected usage:
>
>        Ballroom: Intro Plenary, Breakout tables, Lightning Talks
>
>        Seacliff A+B: Design summit sessions (fishbowl setup)*
>        Seacliff C: Design summit sessions (fishbowl setup)*
>        Seacliff D: Design summit sessions (fishbowl setup)*
>        Marina: Design summit sessions (fishbowl setup)*
>        Bayview B: Design summit sessions (fishbowl setup)*
>
>        Golden Gate: Unconference room (theater setup)*
>        Bayview A: Developer's lounge
>
> The association between rooms+track will be published soon, once the
> revisions on summit.openstack.org are completed.

Thanks, Stefano! Good info. I'll let you know when it's set up.

d

> Cheers,
> stef
>
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


duncan at dreamhost

Apr 11, 2012, 8:13 PM

Post #6 of 12 (461 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

On Wed, Apr 11, 2012 at 5:52 PM, Stefano Maffulli <stefano [at] openstack> wrote:
> On Wed, 2012-04-11 at 14:03 -0700, Matt Joyce wrote:
>> Problem of course is many operators aren't on the design summit
>> contributor list ( ala don't have codes to get into it ) and if it's
>> later it's 500 USD to attend.
>
> There will be over 400 people at the summit, not all of them are
> developers. I expect lots of operators/users have a representation
> there. Will there be enough to justify having this discussion there? I
> don't know but we can try.
>
> On Wed, 2012-04-11 at 17:16 -0400, Duncan McGreggor wrote:
>> That's a really good point. In the post-conference conversations that
>> deal with attendance policy, this should be kept in mind.
>
> We probably should set a date for a post-mortem discussion, after the
> conference. I'm quite sure I'll take a few days off after April 20,
> maybe have a couple of live feedback sessions in the first week of May
> would work?
>
>> In lieu of not being able to attend in person, keep in mind the
>> live-casting that will be done,
>
>
> We're not yet sure to be able to offer this. Wait for an official
> communication.
>
>> in combination with IRC channels.
>
> This we can do: use IRC but there will be only one projector in the
> rooms, not two like at UDS. Each track leader can decide how to use it
> (for IRC or something else).
>
> Since you are already familiar with UDS setup, would you mind setting up
> the IRC channels for each of the rooms at the summit? This is the layout
> of the rooms and their expected usage:
>
>        Ballroom: Intro Plenary, Breakout tables, Lightning Talks
>
>        Seacliff A+B: Design summit sessions (fishbowl setup)*
>        Seacliff C: Design summit sessions (fishbowl setup)*
>        Seacliff D: Design summit sessions (fishbowl setup)*
>        Marina: Design summit sessions (fishbowl setup)*
>        Bayview B: Design summit sessions (fishbowl setup)*
>
>        Golden Gate: Unconference room (theater setup)*
>        Bayview A: Developer's lounge
>
> The association between rooms+track will be published soon, once the
> revisions on summit.openstack.org are completed.

The following channels have been created on Freenode and are registered.

#osds-ballroom
#osds-seacliff-a-b
#osds-seacliff-c
#osds-seacliff-d
#osds-marina
#osds-bayview-a
#osds-bayview-b
#osds-golden-gate

Each channel is also getting logged, viewable via HTTP here:
http://irclogs.osds.cogitat.io/

Feel free to put another logger in there ;-)

At UDS, messages get sent to IRC channels at a countdown interval...
not sure if we have anything that sophisticated for OSDS. At the very
least, we can monitor the times ourselves and post messages to the
channels.

d
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


lzyeval at gmail

Apr 12, 2012, 12:33 AM

Post #7 of 12 (463 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

http://summit.openstack.org/sessions/view/68

I've submitted a proposal on a similar subject but got rejected :) Maybe
because of redundancy.

Looking forward to talking about this at the summit.

Cheers,
LZY

On Thu, Apr 12, 2012 at 11:13 AM, Duncan McGreggor <duncan [at] dreamhost>wrote:

> On Wed, Apr 11, 2012 at 5:52 PM, Stefano Maffulli <stefano [at] openstack>
> wrote:
> > On Wed, 2012-04-11 at 14:03 -0700, Matt Joyce wrote:
> >> Problem of course is many operators aren't on the design summit
> >> contributor list ( ala don't have codes to get into it ) and if it's
> >> later it's 500 USD to attend.
> >
> > There will be over 400 people at the summit, not all of them are
> > developers. I expect lots of operators/users have a representation
> > there. Will there be enough to justify having this discussion there? I
> > don't know but we can try.
> >
> > On Wed, 2012-04-11 at 17:16 -0400, Duncan McGreggor wrote:
> >> That's a really good point. In the post-conference conversations that
> >> deal with attendance policy, this should be kept in mind.
> >
> > We probably should set a date for a post-mortem discussion, after the
> > conference. I'm quite sure I'll take a few days off after April 20,
> > maybe have a couple of live feedback sessions in the first week of May
> > would work?
> >
> >> In lieu of not being able to attend in person, keep in mind the
> >> live-casting that will be done,
> >
> >
> > We're not yet sure to be able to offer this. Wait for an official
> > communication.
> >
> >> in combination with IRC channels.
> >
> > This we can do: use IRC but there will be only one projector in the
> > rooms, not two like at UDS. Each track leader can decide how to use it
> > (for IRC or something else).
> >
> > Since you are already familiar with UDS setup, would you mind setting up
> > the IRC channels for each of the rooms at the summit? This is the layout
> > of the rooms and their expected usage:
> >
> > Ballroom: Intro Plenary, Breakout tables, Lightning Talks
> >
> > Seacliff A+B: Design summit sessions (fishbowl setup)*
> > Seacliff C: Design summit sessions (fishbowl setup)*
> > Seacliff D: Design summit sessions (fishbowl setup)*
> > Marina: Design summit sessions (fishbowl setup)*
> > Bayview B: Design summit sessions (fishbowl setup)*
> >
> > Golden Gate: Unconference room (theater setup)*
> > Bayview A: Developer's lounge
> >
> > The association between rooms+track will be published soon, once the
> > revisions on summit.openstack.org are completed.
>
> The following channels have been created on Freenode and are registered.
>
> #osds-ballroom
> #osds-seacliff-a-b
> #osds-seacliff-c
> #osds-seacliff-d
> #osds-marina
> #osds-bayview-a
> #osds-bayview-b
> #osds-golden-gate
>
> Each channel is also getting logged, viewable via HTTP here:
> http://irclogs.osds.cogitat.io/
>
> Feel free to put another logger in there ;-)
>
> At UDS, messages get sent to IRC channels at a countdown interval...
> not sure if we have anything that sophisticated for OSDS. At the very
> least, we can monitor the times ourselves and post messages to the
> channels.
>
> d
> _______________________________________________
> Openstack-operators mailing list
> Openstack-operators [at] lists
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>


duncan at dreamhost

Apr 13, 2012, 10:58 AM

Post #8 of 12 (464 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

Lyle replied "yes" -- sadly, we can't edit the sessions anymore.

Fortunately, there's the wiki :-) I've updated the session to point to
these blueprints:
http://wiki.openstack.org/Summit/Folsom/DevOps

d

On Wed, Apr 11, 2012 at 4:41 PM, Duncan McGreggor <duncan [at] dreamhost> wrote:
> Lyle, would you mind if I add these to the "Instrumenting OpenStack" session?
>  http://summit.openstack.org/sessions/edit/163
>
> d
>
> On Wed, Apr 11, 2012 at 4:33 PM, Wilkinson, Lyle <lyle.wilkinson [at] hp> wrote:
>> Hi folks,
>>
>>
>>
>> We’ve created a set of 3 blueprints on the topics of health and monitoring,
>> metrics data collection, and cloud inventory maintenance.
>>
>>
>>
>> https://blueprints.launchpad.net/nova/+spec/resource-monitor-alerts-and-notifications
>>
>> https://blueprints.launchpad.net/nova/+spec/utilizationdata
>>
>> https://blueprints.launchpad.net/nova/+spec/cloud-inventory-manager
>>
>>
>>
>> We’re hoping to discuss these at the design summit next week, but currently
>> don’t know if they’ll be part of an existing session or covered in a
>> separate session in one of the open space.  We’ve created some etherpad
>> pages to get the discussion going, so if you have questions, suggestions,
>> etc., feel free to contribute there.
>>
>>
>>
>> http://etherpad.openstack.org/ResourceMonitorAlertsandNotifications
>>
>> http://etherpad.openstack.org/utilizationdata
>>
>> http://etherpad.openstack.org/Cloud-Inventory-Manager
>>
>>
>>
>> Thanks in advance!
>>
>>
>>
>> Lyle Wilkinson
>>
>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack [at] lists
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


stefano at openstack

Apr 13, 2012, 6:48 PM

Post #9 of 12 (464 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

On 04/11/2012 02:52 PM, Stefano Maffulli wrote:
> We're not yet sure to be able to offer this. Wait for an official
> communication.

Here is a brief update regarding the live streaming situation.

Here is the good news:

Cisco kindly offered http://openstack.webex.com. If you get there you'll
see some meetings setup for the days of the Summit, one meeting per each
day, per room.

Zareason kindly offered 9 computers to be put in each room, connected to
the audio equipment available there. Each of Zareason's PC will act as a
'robot-presenter' for Webex.

The good news stop here.

There is bad news: at least 6 of the zareason PCs run 64bit systems, and
64bit Java on Linux is not compatible with Webex (audio issues). Two of
the remaining computers may be too slow to run Webex (I haven't tested
them).

Possible solutions:

- offer live streaming only from 3 rooms (at best, only one at worst)
(which ones?)
- spend a few hours on Sunday wiping out the 6 machines and put 32 bit
systems on
- is there a simpler hack to run 32bit Java on 64bit Ubuntu 11.10
systems?
- these hours will have to be on top of the hours necessary to setup
the rooms, make sure that audio capture really works with the hotel's
audio system etc
- give to session leaders the honor/burden to run Webex sessions from
their own laptops (given how Webex conferencing works, it may be nearly
impossible)

Other ideas? I'm inclined to go with the simplest option, #1. Unless
many (more than 10) people reply to this message asking me to provide
full coverage of the event, I'd go with it. For the other options, I'd
ask for somebody else to take the lead: that means, helping wipe and
install the machines, install java, test them and install them. I'll be
glad to provide all support needed.

Let me know asap, so I can plan the weekend.
stef
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


duncan at dreamhost

Apr 13, 2012, 10:35 PM

Post #10 of 12 (464 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

cc'ing Jorge Castro from Canonical (who will be at the conference...
and maybe the summit?).

Jorge, question below on how to deal with Webex on Ubuntu and limited
time/people resources.

On Fri, Apr 13, 2012 at 9:48 PM, Stefano Maffulli <stefano [at] openstack> wrote:
> On 04/11/2012 02:52 PM, Stefano Maffulli wrote:
>> We're not yet sure to be able to offer this. Wait for an official
>> communication.
>
> Here is a brief update regarding the live streaming situation.
>
> Here is the good news:
>
> Cisco kindly offered http://openstack.webex.com. If you get there you'll
> see some meetings setup for the days of the Summit, one meeting per each
> day, per room.
>
> Zareason kindly offered 9 computers to be put in each room, connected to
> the audio equipment available there. Each of Zareason's PC will act as a
> 'robot-presenter' for Webex.
>
> The good news stop here.
>
> There is bad news: at least 6 of the zareason PCs run 64bit systems, and
> 64bit Java on Linux is not compatible with Webex (audio issues). Two of
> the remaining computers may be too slow to run Webex (I haven't tested
> them).
>
> Possible solutions:
>
> - offer live streaming only from 3 rooms (at best, only one at worst)
> (which ones?)
> - spend a few hours on Sunday wiping out the 6 machines and put 32 bit
> systems on

What about running on a LiveCD? You should be able to install Webex,
as long as the file system is mounted.

Jorge, is that correct? It's been a while since I've used LiveCD.

d

>    - is there a simpler hack to run 32bit Java on 64bit Ubuntu 11.10
> systems?
>    - these hours will have to be on top of the hours necessary to setup
> the rooms, make sure that audio capture really works with the hotel's
> audio system etc
> - give to session leaders the honor/burden to run Webex sessions from
> their own laptops (given how Webex conferencing works, it may be nearly
> impossible)
>
> Other ideas? I'm inclined to go with the simplest option, #1. Unless
> many (more than 10) people reply to this message asking me to provide
> full coverage of the event, I'd go with it. For the other options, I'd
> ask for somebody else to take the lead: that means, helping wipe and
> install the machines, install java, test them and install them. I'll be
> glad to provide all support needed.
>
> Let me know asap, so I can plan the weekend.
> stef
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


stefano at openstack

Apr 14, 2012, 10:03 AM

Post #11 of 12 (459 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

This is an awesome and elegant workaround. We'll do this.

Let's meet on Sunday afternoon at Rackspace SF to complete this task. Let me know if you want to join.

Stef

--
On the road, expect brevity and typos
In giro, errori e brevità inclusi

On Apr 14, 2012, at 9:23 AM, "Jorge O. Castro" <jorge [at] ubuntu> wrote:

> On Sat, Apr 14, 2012 at 1:35 AM, Duncan McGreggor <duncan [at] dreamhost> wrote:
>>
>> What about running on a LiveCD? You should be able to install Webex,
>> as long as the file system is mounted.
>>
>> Jorge, is that correct? It's been a while since I've used LiveCD.
>
> This will work (I've done this sort of thing in the past.). What might
> work better is running off of a liveUSB stick with persistence
> enabled, so you can set them one prior to the event with everything
> you need and then just clone them; then you'd be able to reuse them if
> you need to swap out hardware.
>
> --
> Jorge Castro
> Canonical Ltd.
> http://cloud.ubuntu.com
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators


duncan at dreamhost

Apr 14, 2012, 5:01 PM

Post #12 of 12 (459 views)
Permalink
Re: [Openstack] Health & Monitoring Blueprints [In reply to]

On Sat, Apr 14, 2012 at 12:23 PM, Jorge O. Castro <jorge [at] ubuntu> wrote:
> On Sat, Apr 14, 2012 at 1:35 AM, Duncan McGreggor <duncan [at] dreamhost> wrote:
>>
>> What about running on a LiveCD? You should be able to install Webex,
>> as long as the file system is mounted.
>>
>> Jorge, is that correct? It's been a while since I've used LiveCD.
>
> This will work (I've done this sort of thing in the past.). What might
> work better is running off of a liveUSB stick with persistence
> enabled, so you can set them one prior to the event with everything
> you need and then just clone them; then you'd be able to reuse them if
> you need to swap out hardware.

You are the MAN, Jorge! Thanks :-)

See you in a day or so!

d
_______________________________________________
Openstack-operators mailing list
Openstack-operators [at] lists
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators

OpenStack operators RSS feed   Index | Next | Previous | View Threaded
 
 


Interested in having your list archived? Contact Gossamer Threads
 
  Web Applications & Managed Hosting Powered by Gossamer Threads Inc.