Why? Can you please clarify.
Igor Laskovy
facebook.com/igor.laskovy
Kiev, Ukraine
On Jun 15, 2012 1:55 AM, Christian Parpart tra...@gmail.com wrote:
I don't think putting the controller node completely into a VM is a good
advice,
at least when speaking of nova-scheduler and nova-api (if
Hi Grabriel,
let's discuss the blueprint [1] on the list.
On 06/14/2012 10:36 PM, Gabriel Hurley wrote:
Blueprint changed by Gabriel Hurley:
Whiteboard set to:
After discussing this with both the Horizon core team and Django's
security czar/core committer Paul McMillan, we've decided the
Hey,
well, I said I might be wrong because I have no clear vision on how
OpenStack works in
its deepest detail, however, I would not like to depend on a controller
node that
is inside a virtual machine, controlled by compute nodes, that are
controlled by the controller
node. This sounds quite
Dan Prince wrote:
Hey Jim,
Any updates or new ideas on the cause of the intermittent hangs?
The issue is discussed and fixed on:
https://bugs.launchpad.net/nova/+bug/1012595
It was traced down to absence of your own hostname in /etc/hosts on
HPCloud/Precise images, which makes devstack fail.
I am using OpenStack for my little lab for a short time too))
Ok, you are right of course, but I meant a some another design when told
about virtualization controller nodes.
It is can be only two dedicated hypetvisor with dedicated share/drbd
between them. This hypervisors will be standalone,
I know there is some work in the XenAPI driver to make it resilient to these
kinds of failures (to allow frequent updates of the nova code), and I think
there were plans for the work to be reused in the Libvirt driver.
AFAIK, in Essex and lower, bad things can happen if you don't wait for all
Hi,
The nova-novncproxy reads some parameters in /etc/nova/nova.conf file. First
you need to configure your cloud controller to enable vnc
novncproxy_host = 0.0.0.0
novncproxy_port = 6080
and in the nova compute nodes you need something like this
I don't see this as an either-or type of thing.
Totally agree with Mark that the APIs need to be more clearly documented
and that should be independent of any kind of IDL (ala WADL) artifact. I
say this mainly because I think we always need to have something that's
human readable and not
So, making cloud controller node highly available using Corosync/Pacemaker
does not really avoid potential issue which you have mentioned below
(recover from half completed tasks), correct?
Igor Laskovy
facebook.com/igor.laskovy
Kiev, Ukraine
On Jun 15, 2012 1:36 PM, John Garbutt
+1Over-reliance on WADL will only make it more challenging to gracefully evolve the APIs such that implementations can be forwards and/or backwards compatible, especially when exchanging XML based on an XSD that is not carefully crafted with proper extensibility points incorporated throughout the
On Wed, Jun 13, 2012 at 4:26 PM, Caitlin Bestler
caitlin.best...@nexenta.com wrote:
Doug Hellmann wrote:
** **
There are a couple of other alternatives:
** **
1. We could move notification handling into its own daemon to get it out
of the collector. This new daemon would
Hi, Brian!
Thank you for advices for my glance patch!
I would like to ask your help.
I saw the following report for the latest patch edition:
- https://jenkins.openstack.org/job/gate-glance-merge/825/ : SUCCESS
- https://jenkins.openstack.org/job/gate-glance-pep8/1007/ : SUCCESS
-
Keystone is using XSD1.1 already.
Mark, I totally agree with you in that we need a contract to a service, may
it WADL or whatever IDL you use... For us, we have used WADL as a mere
contract (among our services and QA), and that's about it. We don't generate
code from WADL, nor try to bake
Hey,
We're hoping to do Nova, Glance, Keystone and Horizon 2012.1.1 releases
Thursday (Jun 21).
I've add a bunch of details here:
http://wiki.openstack.org/StableBranchRelease
The list of issues fixed so far can be seen here:
https://launchpad.net/nova/+milestone/2012.1.1
Hi,
For those who are affected by the dnsmasq/vlan issues on Ubuntu, I have
uploaded a fix for precise-proposed. It should be available for testing
of the fix soon. You will have to turn on precise-proposed on your
servers to test the fix.
Regards
chuck
On Fri, 15 Jun 2012 20:19:28 +0800
李跃洲
Totally agree.
Note that we are using WADL today to create documentation artifacts. So
http://api.openstack.org/ is generated from WADLs as are good chunks of the
books on http://docs.openstack.org/. We're also using WADL for validation and
testing at Rackspace internally, and I'm sure
All of the XSDs produced so far use XSD 1.1.
-jOrGe W.
On Jun 15, 2012, at 8:57 AM, Christopher B Ferris wrote:
+1
Over-reliance on WADL will only make it more challenging to gracefully evolve
the APIs such that implementations can be forwards and/or backwards compatible,
especially when
Howdy all,
I've spent the past few days slogging through the initial steps of
getting OpenStack and running and I seem to have hit a wall. If this
isn't the right list for this question, please feel free to direct me
elsewhere.
I have two systems running the OpenStack components right now. The
Hi everyone!
I want to know the vcpu hours per instance, in horizon In nova dashboard I
can see the total hours for the tenant, I want to see the hours for each
instance, which together must be equal to total. How can I do that?
I think the api does not have some method like that, What do you
Well, apologies for the stupid subject line. In the interests of
sewing as much confusion as possible, here's the question that was
supposed to go along with that subject:
nova.conf appears to sport several configuration options related to
glance, including:
- glance_host
- glance_port
-
Hey Lars,
Sadly I don't have much in the way of a solution for you, but I do have
some suggestions. Comments inline.
On 6/15/12 4:17 PM, Lars Kellogg-Stedman l...@seas.harvard.edu wrote:
Howdy all,
I've spent the past few days slogging through the initial steps of
getting OpenStack and
I'm used to using rabbit, but I did notice you didn't include a
nova-scheduler in your list above...
There is a nova-scheduler service running on the controller:
Binary Host Zone Status
State Updated_At
nova-cert
I don't really know anything about AMQ or how OpenStack utilizes the
message broker. Are there any commands I can run that would exercise
the message broker and confirm whether or not it is working correctly?
For what it's worth:
qpid provies a test suite (qpid-python-test that appears to
Hi Lars -
Sounds like you're really looking for a conceptual understanding and I
like that! Keystone does maintain the service catalog, and the Image
service (glance) needs specific entries. See
http://docs.openstack.org/essex/openstack-compute/install/yum/content/keystone-concepts.html.
I
On Fri, 2012-06-15 at 16:26 -0400, Lars Kellogg-Stedman wrote:
nova.conf appears to sport several configuration options related to
glance, including:
- glance_host
- glance_port
- glance_api_servers
These seem suspiciously similar.
Indeed.
Do they do the same thing?
Yes, they do.
To the points Sascha raised, and in particular in response to the code method
suggested here
(https://github.com/saschpe/horizon/commit/1414d538d65d2d3deb981db0ab9e888a3c96a149)
I think we are largely in agreement except for one point:
I have no problem with this approach for development, or
*OpenStack Community Newsletter --- June 15*
Highlights of the week
Announcing OpenStack Asia/Pacific Conference 2012
http://www.openstack.org/blog/2012/06/announcing-openstack-asiapacific-conference-2012/
The OpenStack Asia/Pacific community is hosting a large
Thanks everyone for this great job. Will be testing in debian this weekend.
Ghe Rivero
El 15/06/2012 19:05, Mark McLoughlin mar...@redhat.com escribió:
Hey,
We're hoping to do Nova, Glance, Keystone and Horizon 2012.1.1 releases
Thursday (Jun 21).
I've add a bunch of details here:
Hey all,
it now just happened twice again, both just today. and the last at 22:00
UTC, with
the following in the nova-network's syslog:
root@gw1:/var/log# grep 'dnsmasq.*10889' daemon.log
Jun 15 17:39:32 cesar1 dnsmasq[10889]: started, version v2.62-7-g4ce4f37
cachesize 150
Jun 15 17:39:32
The reason these options have not gone away is probably a combination of
supporting non-Keystone authentication and general programmer laziness…
Kevin,
Thanks for the reply, makes sense. Just to make sure I understand
things, it sounds like Nova does not currently query Keystone for
endpoints
30 matches
Mail list logo
