[Openstack] Why did the instancemonitor disappear in the Diablo?
Dear All Why did the instancemonitor disappear in the Diablo release? For example, following files can be found in the Diablo milestone-3. But they're removed in the Diablo milestone-4 and the last release. bin/nova-instancemonitor nova/compute/monitor.py Can someone explain the reason why these are removed and whether there is any plan to replace them. Joonwon Lee ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Why did the instancemonitor disappear in the Diablo?
They were removed because they no longer worked correctly and they were based on twisted code. There is no current plan to replace them. Rather than generating graphs via internal software, it makes more sense to write very simple plugins for external monitoring services like munin. Example using nova db calls: https://github.com/cloudbuilders/openstack-munin/blob/master/nova_floating_ips Example using custom sql: https://github.com/cloudbuilders/openstack-munin/blob/master/nova_instance_timing Existing ones for network and block monitoring: http://honk.sigxcpu.org/projects/libvirt/ Vish On Sep 29, 2011, at 2:58 AM, 이준원 (Joonwon Lee) wrote: Dear All Why did the instancemonitor disappear in the Diablo release? For example, following files can be found in the Diablo milestone-3. But they're removed in the Diablo milestone-4 and the last release. bin/nova-instancemonitor nova/compute/monitor.py Can someone explain the reason why these are removed and whether there is any plan to replace them. Joonwon Lee ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [libvirt] [RFC PATCH] lxc: don't return error on GetInfo when cgroups not yet set up
Quoting Daniel P. Berrange (berra...@redhat.com):
On Wed, Sep 28, 2011 at 02:14:52PM -0500, Serge E. Hallyn wrote:
Nova (openstack) calls libvirt to create a container, then
periodically checks using GetInfo to see whether the container
is up. If it does this too quickly, then libvirt returns an
error, which in libvirt.py causes an exception to be raised,
the same type as if the container was bad.
lxcDomainGetInfo(), holds a mutex on 'dom' for the duration of
its execution. It checks for virDomainObjIsActive() before
trying to use the cgroups.
lxcDomainStart(), holds the mutex on 'dom' for the duration of
its execution, and does not return until the container is running
and cgroups are present.
Yup, now that you mention it, I do see that. So this shouldn't be
happening. Can't explain it, but copious fprintf debugging still
suggests it is :)
Is it possible that vm-def-id is not being set to -1 when it is
first defined, and I'm catching it between define and start? I
would think that would show up as much more broken, though I'm
not seeing where vm-def-id gets set to -1 during domain definition.
Well, I'll keep digging then. Thanks for setting me straight on
the mutex!
Similarly when we delete the cgroups, we again hold the lock
on 'dom'.
Thus any time viDomainObjIsActive() returns true, AFAICT, we have
guaranteed that the cgroup does in fact exist.
So can't see how control gets to the 'else' part of this
condition if the cgroups don't exist like you describe.
if (!virDomainObjIsActive(vm) || driver-cgroup == NULL) {
info-cpuTime = 0;
info-memory = vm-def-mem.cur_balloon;
} else {
if (virCgroupForDomain(driver-cgroup, vm-def-name, cgroup, 0) !=
0) {
lxcError(VIR_ERR_INTERNAL_ERROR,
_(Unable to get cgroup for %s), vm-def-name);
goto cleanup;
}
What libvirt version were you seeing this behaviour with ?
0.9.2
thanks,
-serge
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] Swift git differences between launchpad vs github milestone-proposed branch history
Hi,
I originally imported the swift milestone-proposed branch
(lp:~hudson-openstack/swift/milestone-proposed) from launchpad into a git
repository locally, sometime after the 1.4.1 release and synced again after the
1.4.2. This was before it was clear that the swift project was definitely
moving to use git and the repo on github would definitely be the public git
repo.
In looking to now switch to pulling from the project repo on github and I've
noticed a few discrepancies.
Tag 1.4.1 within my local repo, which was imported from bzr, points to a
different commit than what the github repository points to. I'm wondering how
that has come to be?
github points to the following commit as being 1.4.1
$ git ls-remote openstack | grep refs/tags/1.4.1
9ab33970b58b8219245bfd89e2ad9442c0e94f17refs/tags/1.4.1
(https://github.com/openstack/swift/commit/9ab33970b58b8219245bfd89e2ad9442c0e94f17)
$ git log -n1 9ab33970b58b8219245bfd89e2ad9442c0e94f17
commit 9ab33970b58b8219245bfd89e2ad9442c0e94f17
Merge: 8526098 c4f0b55
Author: John Dickinson
john.dickin...@rackspace.commailto:john.dickin...@rackspace.com
Date: Tue Jun 14 16:37:02 2011 +
updated changelog for 1.4.1
Bzr points to the following change as being tagged for 1.4.1:
http://bazaar.launchpad.net/~hudson-openstack/swift/milestone-proposed/revision/305
* Committer: Tarmac
* Author(s): Thierry Carrez
* Date: 2011-06-20 14:42:27
* mfrom: (304.1.1
milestone-proposed)http://bazaar.launchpad.net/%7Ehudson-openstack/swift/milestone-proposed/revision/304.1.1
* Revision ID: tarmac-20110620144227-n6ko7ns5s83aceh9
Tags: 1.4.1
Final 1.4.1 versioning for immediate release.
Looking at the imported repo in git, I can see the following differences
between what is tagged in github versus what was tagged in launchpad.
(openstack is the remote name I have for https://github.com/openstack/swift.git)
$ git log --graph --decorate --right-only $(git ls-remote openstack | grep
refs/tags/1.4.1 | awk '{print $1'})...1.4.1
* commit d8f39dbaaeab646117b8267a33c606a21dbef29b (tag: 1.4.1,
origin/upstream/milestone-proposed)
|\ Merge: 3ad61bd 1dec5d4
| | Author: Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org
| | Date: Mon Jun 20 14:42:27 2011 +
| |
| | Final 1.4.1 versioning for immediate release.
| |
| * commit 1dec5d45c82a92fde49d7d7ba478cebce52fc162
|/ Author: Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org
| Date: Mon Jun 20 14:37:17 2011 +0200
|
| Final 1.4.1 versioning
|
* commit 3ad61bd15cdf90b91c3834c6444e56a4d4436bd6
|\ Merge: 60f9cbf d41490c
| | Author: David Goetz
david.go...@rackspace.commailto:david.go...@rackspace.com
| | Date: Wed Jun 15 14:57:34 2011 +
| |
| | Merge 1.4.1 development from trunk (rev312)
| |
| * commit d41490c38477205c6619a8c79857973474497bad
|/ Merge: 60f9cbf 9ab3397
| Author: Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org
| Date: Wed Jun 15 11:11:51 2011 +0200
|
| Merge 1.4.1 development from trunk (rev312)
|
snip 2 additional commits
Commit d41490c38477205c6 merges the commit marked as 1.4.1 in github
(9ab33970b58b82192) onto the milestone-proposed branch from launchpad.
I've looked at the tags from bzr on launchpad and confirmed that they point to
same changes as my local tree for 1.4.1, so I'm wondering was the tag moved on
launchpad sometime after the import into the github repository?
I see a similar thing happening with the 1.4.2 tag. What is tagged in github is
not quite the same as the tag imported from launchpad. Also confirmed that the
import of the tag from bzr to my local git repo is pointing to the same data,
so it looks like the tags on launchpad for swift for 1.4.1 and 1.4.2 don't
match what is tagged in github.
$ git log --graph --decorate --right-only $(git ls-remote openstack | grep
refs/tags/1.4.2 | awk '{print $1'})...1.4.2
* commit c4f718ff7c565d7b40e10c881506be009e6cbbd7 (tag: 1.4.2,
bzr/upstream/milestone-propose
|\ Merge: 389e407 c509923
| | Author: Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org
| | Date: Wed Jul 27 14:33:19 2011 +
| |
| | Final 1.4.2 versioning
| |
| * commit c5099233521ce7d90e985aa32a5e156b48a7b4c4
|/ Author: Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org
| Date: Wed Jul 27 15:58:51 2011 +0200
|
| Final 1.4.2 versioning
|
* commit 389e4071ddd34037f2b1f7eb13c59b49256ed82d
|\ Merge: d8f39db f9092e2
| | Author: gholt gh...@rackspace.commailto:gh...@rackspace.com
| | Date: Tue Jul 26 09:08:37 2011 +
| |
| | Merge 1.4.2 development from trunk (rev331)
| |
| * commit f9092e20a41dba3fe616bd7573deaa46cbdadcb3
|/ Merge: d8f39db a9c0a26
| Author: Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org
| Date: Tue Jul 26 10:42:21 2011 +0200
|
| Merge 1.4.2 development from trunk (rev331)
snip commits to do with 1.4.1
Commit a9c0a26 is what is tagged in github as
Re: [Openstack] Swift git differences between launchpad vs github milestone-proposed branch history
The code that was on github was an unofficial mirror that I was maintaining.
With each release, I added the tag to github repo. It looks like I didn't tag
at the same commit as the (at the time) official repo. This is because the
milestone-proposed branch did not exist in the unofficial github mirror.
When we moved to github, I think the code that was already there was used (why
reimport if everything is already there?). This is what lead to the tag
discrepancy. There is no significant difference in the eg 1.4.1 tags between
what's tagged now and what was tagged in bzr. The only difference should be the
final versioning. Functionally, the code at each of the two tags should be
identical.
I apologize for the discrepancy. I think the risk of future problems is much
lower now that the github repo is officially managed.
--John
On Sep 29, 2011, at 8:09 AM, Bailey, Darragh wrote:
Hi,
I originally imported the swift milestone-proposed branch
(lp:~hudson-openstack/swift/milestone-proposed) from launchpad into a git
repository locally, sometime after the 1.4.1 release and synced again after
the 1.4.2. This was before it was clear that the swift project was definitely
moving to use git and the repo on github would definitely be the public git
repo.
In looking to now switch to pulling from the project repo on github and I've
noticed a few discrepancies.
Tag 1.4.1 within my local repo, which was imported from bzr, points to a
different commit than what the github repository points to. I'm wondering how
that has come to be?
github points to the following commit as being 1.4.1
$ git ls-remote openstack | grep refs/tags/1.4.1
9ab33970b58b8219245bfd89e2ad9442c0e94f17refs/tags/1.4.1
(https://github.com/openstack/swift/commit/9ab33970b58b8219245bfd89e2ad9442c0e94f17)
$ git log -n1 9ab33970b58b8219245bfd89e2ad9442c0e94f17
commit 9ab33970b58b8219245bfd89e2ad9442c0e94f17
Merge: 8526098 c4f0b55
Author: John Dickinson
john.dickin...@rackspace.commailto:john.dickin...@rackspace.com
Date: Tue Jun 14 16:37:02 2011 +
updated changelog for 1.4.1
Bzr points to the following change as being tagged for 1.4.1:
http://bazaar.launchpad.net/~hudson-openstack/swift/milestone-proposed/revision/305
* Committer: Tarmac
* Author(s): Thierry Carrez
* Date: 2011-06-20 14:42:27
* mfrom: (304.1.1
milestone-proposed)http://bazaar.launchpad.net/%7Ehudson-openstack/swift/milestone-proposed/revision/304.1.1
* Revision ID: tarmac-20110620144227-n6ko7ns5s83aceh9
Tags: 1.4.1
Final 1.4.1 versioning for immediate release.
Looking at the imported repo in git, I can see the following differences
between what is tagged in github versus what was tagged in launchpad.
(openstack is the remote name I have for
https://github.com/openstack/swift.git)
$ git log --graph --decorate --right-only $(git ls-remote openstack | grep
refs/tags/1.4.1 | awk '{print $1'})...1.4.1
* commit d8f39dbaaeab646117b8267a33c606a21dbef29b (tag: 1.4.1,
origin/upstream/milestone-proposed)
|\ Merge: 3ad61bd 1dec5d4
| | Author: Thierry Carrez
thie...@openstack.orgmailto:thie...@openstack.org
| | Date: Mon Jun 20 14:42:27 2011 +
| |
| | Final 1.4.1 versioning for immediate release.
| |
| * commit 1dec5d45c82a92fde49d7d7ba478cebce52fc162
|/ Author: Thierry Carrez
thie...@openstack.orgmailto:thie...@openstack.org
| Date: Mon Jun 20 14:37:17 2011 +0200
|
| Final 1.4.1 versioning
|
* commit 3ad61bd15cdf90b91c3834c6444e56a4d4436bd6
|\ Merge: 60f9cbf d41490c
| | Author: David Goetz
david.go...@rackspace.commailto:david.go...@rackspace.com
| | Date: Wed Jun 15 14:57:34 2011 +
| |
| | Merge 1.4.1 development from trunk (rev312)
| |
| * commit d41490c38477205c6619a8c79857973474497bad
|/ Merge: 60f9cbf 9ab3397
| Author: Thierry Carrez
thie...@openstack.orgmailto:thie...@openstack.org
| Date: Wed Jun 15 11:11:51 2011 +0200
|
| Merge 1.4.1 development from trunk (rev312)
|
snip 2 additional commits
Commit d41490c38477205c6 merges the commit marked as 1.4.1 in github
(9ab33970b58b82192) onto the milestone-proposed branch from launchpad.
I've looked at the tags from bzr on launchpad and confirmed that they point
to same changes as my local tree for 1.4.1, so I'm wondering was the tag
moved on launchpad sometime after the import into the github repository?
I see a similar thing happening with the 1.4.2 tag. What is tagged in github
is not quite the same as the tag imported from launchpad. Also confirmed that
the import of the tag from bzr to my local git repo is pointing to the same
data, so it looks like the tags on launchpad for swift for 1.4.1 and 1.4.2
don't match what is tagged in github.
$ git log --graph --decorate --right-only $(git ls-remote openstack | grep
refs/tags/1.4.2 | awk '{print $1'})...1.4.2
* commit c4f718ff7c565d7b40e10c881506be009e6cbbd7 (tag:
[Openstack] NovaCompute on XenServer6
Hi all, I'm about to migrate my nova-compute nodes from XenServer 5.6 to the new XenServer 6: do I need updated plugins? Are the instructions reported here http://wiki.openstack.org/XenServerDevelopment still a good reference? What about vlan networking? Will the default use of openswitch in XS6 change something? Thanks a lot Giuseppe ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] dashaboard+keystone+nova+glance work well？
There are a few bugs specific to admin functions in Keystone. It's about 95% there now and when those last issues are resolved we will be back in business. Best, Devin On Sep 28, 2011, at 6:37 PM, andi abes wrote: is this just to avoid the need for the long lived token, or are there other issues in dash/keystone integration? 2011/9/28 Devin Carlen devin.car...@gmail.com We should have a drop of Keystone by the end of the week that fully support Diablo. This will fix the Dashboard issues as well. Thanks, Devin On Sep 28, 2011, at 12:31 AM, Jesse Andrews wrote: at various points in time they have worked together. We (cloudbuilders) keep a list of repositories that work well together. # compute service NOVA_REPO=https://github.com/openstack/nova.git NOVA_BRANCH=2011.3 # image catalog service GLANCE_REPO=https://github.com/cloudbuilders/glance.git GLANCE_BRANCH=diablo # unified auth system (manages accounts/tokens) KEYSTONE_REPO=https://github.com/cloudbuilders/keystone.git KEYSTONE_BRANCH=diablo # a websockets/html5 or flash powered VNC console for vm instances NOVNC_REPO=https://github.com/cloudbuilders/noVNC.git NOVNC_BRANCH=master # django powered web control panel for openstack DASH_REPO=https://github.com/cloudbuilders/openstack-dashboard.git DASH_BRANCH=master # python client library to nova that dashboard (and others) use NOVACLIENT_REPO=https://github.com/cloudbuilders/python-novaclient.git NOVACLIENT_BRANCH=master # openstackx is a collection of extensions to openstack.compute nova # that is *deprecated*. The code is being moved into python-novaclient nova. OPENSTACKX_REPO=https://github.com/cloudbuilders/openstackx.git OPENSTACKX_BRANCH=diablo On Tue, Sep 27, 2011 at 7:11 PM, shake chen shake.c...@gmail.com wrote: No， Now the Dashbaord can not working. https://bugs.launchpad.net/openstack-dashboard/+bug/855142 I think need the bug beed fixed. On Wed, Sep 28, 2011 at 9:31 AM, l jv ljv...@gmail.com wrote: hi is there anybody config dashaboard+keystone+nova+glance sucess and work well? when i do as the http://docs.openstack.org/,but it does not work well,always has some wrong when use dashboard(glance and nova work well). So somebody can write a detail config process doc ？ thans a lot ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 陈沙克 手机：13661187180 msn：shake.c...@hotmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] NovaCompute on XenServer6
On Thu, Sep 29, 2011 at 11:45 AM, Giuseppe Civitella giuseppe.civite...@gmail.com wrote: Hi all, I'm about to migrate my nova-compute nodes from XenServer 5.6 to the new XenServer 6: do I need updated plugins? It's a good idea to run the latest xapi plugins. Are the instructions reported here http://wiki.openstack.org/XenServerDevelopment still a good reference? Yes. What about vlan networking? Will the default use of openswitch in XS6 change something? Anything in particular you are concerned about? Let us know if you find any issues. I would suggest taking a look at: http://wiki.openstack.org/Quantum which comes with an Open vSwitch plugin. Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] dashaboard+keystone+nova+glance work well？
perhaps unrelated, but I added a branch to novaclient a while ago that allows you to reuse a token, so you don't have to re-auth. This is, of course, library only ... not cmdline. From: openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net [openstack-bounces+sandy.walsh=rackspace@lists.launchpad.net] on behalf of Devin Carlen [devin.car...@gmail.com] Sent: Thursday, September 29, 2011 2:05 PM To: andi abes Cc: openstack@lists.launchpad.net Subject: Re: [Openstack] dashaboard+keystone+nova+glance work well？ There are a few bugs specific to admin functions in Keystone. It's about 95% there now and when those last issues are resolved we will be back in business. Best, Devin On Sep 28, 2011, at 6:37 PM, andi abes wrote: is this just to avoid the need for the long lived token, or are there other issues in dash/keystone integration? 2011/9/28 Devin Carlen devin.car...@gmail.commailto:devin.car...@gmail.com We should have a drop of Keystone by the end of the week that fully support Diablo. This will fix the Dashboard issues as well. Thanks, Devin On Sep 28, 2011, at 12:31 AM, Jesse Andrews wrote: at various points in time they have worked together. We (cloudbuilders) keep a list of repositories that work well together. # compute service NOVA_REPO=https://github.com/openstack/nova.git NOVA_BRANCH=2011.3 # image catalog service GLANCE_REPO=https://github.com/cloudbuilders/glance.git GLANCE_BRANCH=diablo # unified auth system (manages accounts/tokens) KEYSTONE_REPO=https://github.com/cloudbuilders/keystone.git KEYSTONE_BRANCH=diablo # a websockets/html5 or flash powered VNC console for vm instances NOVNC_REPO=https://github.com/cloudbuilders/noVNC.git NOVNC_BRANCH=master # django powered web control panel for openstack DASH_REPO=https://github.com/cloudbuilders/openstack-dashboard.git DASH_BRANCH=master # python client library to nova that dashboard (and others) use NOVACLIENT_REPO=https://github.com/cloudbuilders/python-novaclient.git NOVACLIENT_BRANCH=master # openstackx is a collection of extensions to openstack.compute nova # that is *deprecated*. The code is being moved into python-novaclient nova. OPENSTACKX_REPO=https://github.com/cloudbuilders/openstackx.git OPENSTACKX_BRANCH=diablo On Tue, Sep 27, 2011 at 7:11 PM, shake chen shake.c...@gmail.commailto:shake.c...@gmail.com wrote: No， Now the Dashbaord can not working. https://bugs.launchpad.net/openstack-dashboard/+bug/855142 I think need the bug beed fixed. On Wed, Sep 28, 2011 at 9:31 AM, l jv ljv...@gmail.commailto:ljv...@gmail.com wrote: hi is there anybody config dashaboard+keystone+nova+glance sucess and work well? when i do as the http://docs.openstack.org/,but it does not work well,always has some wrong when use dashboard(glance and nova work well). So somebody can write a detail config process doc ？ thans a lot ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- 陈沙克 手机：13661187180 msn：shake.c...@hotmail.commailto:shake.c...@hotmail.com ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.netmailto:openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp This email may include confidential information. If you received it in error, please delete it. ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] NovaCompute on XenServer6
What about vlan networking? Will the default use of openswitch in XS6 change something? No, the Nova XenServer integration is done through XenAPI which abstracts the differences between the Linux bridge stack and vSwitch for operations like creating VLANs. The exception to that is the port isolation support which configures the vSwitch directly and that Ewan updated recently. That work is based on the vSwitch version in XS6. Carl On 9/29/11 11:17 AM, Todd Deshane todd.desh...@xen.org wrote: On Thu, Sep 29, 2011 at 11:45 AM, Giuseppe Civitella giuseppe.civite...@gmail.com wrote: Hi all, I'm about to migrate my nova-compute nodes from XenServer 5.6 to the new XenServer 6: do I need updated plugins? It's a good idea to run the latest xapi plugins. Are the instructions reported here http://wiki.openstack.org/XenServerDevelopment still a good reference? Yes. What about vlan networking? Will the default use of openswitch in XS6 change something? Anything in particular you are concerned about? Let us know if you find any issues. I would suggest taking a look at: http://wiki.openstack.org/Quantum which comes with an Open vSwitch plugin. Thanks, Todd -- Todd Deshane http://www.linkedin.com/in/deshantm http://www.xen.org/products/cloudxen.html http://runningxen.com/ ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
[Openstack] 55PB storage cloud hosted using Swift
In case you missed it, SDSC is hosting a commercial 55 petabyte storage cloud using Swift: http://arstechnica.com/business/news/2011/09/supercomputing-center-targets-55-petabyte-storage-at-academics-students.ars https://cloud.sdsc.edu/hp/index.php Congrats to the Swift team! Brian - Brian Schott, CTO Nimbis Services, Inc. brian.sch...@nimbisservices.com ph: 443-274-6064 fx: 443-274-6060 smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 55PB storage cloud hosted using Swift
clarification: 5.5PB On Sep 29, 2011, at 3:00 PM, Brian Schott wrote: In case you missed it, SDSC is hosting a commercial 55 petabyte storage cloud using Swift: http://arstechnica.com/business/news/2011/09/supercomputing-center-targets-55-petabyte-storage-at-academics-students.ars https://cloud.sdsc.edu/hp/index.php Congrats to the Swift team! Brian - Brian Schott, CTO Nimbis Services, Inc. brian.sch...@nimbisservices.com ph: 443-274-6064 fx: 443-274-6060 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp smime.p7s Description: S/MIME cryptographic signature ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] 55PB storage cloud hosted using Swift
Anyone else think of office space just then? Still a great accomplishment! On Thu, Sep 29, 2011 at 1:37 PM, John Dickinson m...@not.mn wrote: clarification: 5.5PB On Sep 29, 2011, at 3:00 PM, Brian Schott wrote: In case you missed it, SDSC is hosting a commercial 55 petabyte storage cloud using Swift: http://arstechnica.com/business/news/2011/09/supercomputing-center-targets-55-petabyte-storage-at-academics-students.ars https://cloud.sdsc.edu/hp/index.php Congrats to the Swift team! Brian - Brian Schott, CTO Nimbis Services, Inc. brian.sch...@nimbisservices.com ph: 443-274-6064 fx: 443-274-6060 ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Improving meetbot reports
On Wed, 2011-09-28 at 11:06 -0700, Stefano Maffulli wrote: I can read the latest ones and see if I spot patterns. Anybody that feels strongly for this please do the same and send your analysis to the list for further discussion. I did some reading and I found examples for Good summaries http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-08-15-20.07.html http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-07-11-20.02.html and summaries that could be improved: http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-27-21.03.html http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-20-21.02.html http://eavesdrop.openstack.org/meetings/openstack-meeting/2011/openstack-meeting.2011-09-13-22.02.html One thing that seems clear is that the #info tag is not always used by the moderator, resulting in summaries that are way too dry to be meaningful. Some of the summaries have only a list of topic. On the other thand when #info is used more often, summaries seem to be much more intelligible. Do you think that adding a brief #info summary before changing topic would be a good habit? /stef ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Messaging level auth
Joshua, your question scares me :) Actually you can define user/pass for rabbitmq: See in rpc/impl_kombu.py, which is used by default: 308 self.params = dict(hostname=FLAGS.rabbit_host, 309 port=FLAGS.rabbit_port, 310 userid=FLAGS.rabbit_userid, 311 password=FLAGS.rabbit_password, 312 virtual_host=FLAGS.rabbit_virtual_host) But this seems to be not secured connection, since I don't see here usage of SSL. In rpc/impl_carrot.py: 66 params = dict(hostname=FLAGS.rabbit_host, 67 port=FLAGS.rabbit_port, * 68 ssl=FLAGS.rabbit_use_ssl,* 69 userid=FLAGS.rabbit_userid, 70 password=FLAGS.rabbit_password, 71 virtual_host=FLAGS.rabbit_virtual_host) but I never tried this carrot and don't know if it works. Can someone else clarify the question? It seems important in terms of security. Thanks, On Wed, Sep 21, 2011 at 2:20 PM, Joshua Harlow harlo...@yahoo-inc.comwrote: A quick security question. Is there any plan to force authentication/authorization of the rabbitmq messages? Right now it seems like keystone (tbd) will protect the external-openstack layers but what about the openstack-openstack layers. If someone got access to the rabbitmq it seems like without this kind of layer bad things could happen (create me 1000 nodes...). Has there been any thought in that area? -Josh ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp -- Mike Scherbakov ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
Re: [Openstack] [libvirt] [RFC PATCH] lxc: don't return error on GetInfo when cgroups not yet set up
Quoting Daniel P. Berrange (berra...@redhat.com): On Wed, Sep 28, 2011 at 02:14:52PM -0500, Serge E. Hallyn wrote: Nova (openstack) calls libvirt to create a container, then periodically checks using GetInfo to see whether the container is up. If it does this too quickly, then libvirt returns an error, which in libvirt.py causes an exception to be raised, the same type as if the container was bad. lxcDomainGetInfo(), holds a mutex on 'dom' for the duration of its execution. It checks for virDomainObjIsActive() before trying to use the cgroups. Yes, it does, but lxcDomainStart(), holds the mutex on 'dom' for the duration of its execution, and does not return until the container is running and cgroups are present. No. It calls the lxc_controller with --background. The controller main task in turn exits before the cgroups have been set up. There is the race. -serge ___ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
