Hi All,
Nova scheduler decides the compute host for the VM instances to run based
on the selected scheduling algorithm. Is it possible to choose a particular
compute host for each request where a VM instance should run ?
--
Thanks & Regards
Neelakantam Gaddam
__
you should use admin credentials ,then run instances by adding an
option --force_hosts=node1 to nova boot .
2012/6/19 Neelakantam Gaddam :
> Hi All,
>
> Nova scheduler decides the compute host for the VM instances to run based
> on the selected scheduling algorithm. Is it possible to choose
On 06/19/2012 04:55 AM, Paul McMillan wrote:
>> Ah, you're thinking of a setup where there are multiple dashboard VMs
>> behind a load-balancer serving requests. Indeed, there the dashboard
>> instances should either share the SECRET_KEY or the load-balancer has to
>> make sure that all requests of
Hi, you can find here the available filters : http://nova.openstack.org/devref/filter_scheduler.htmlHere are the ones you might look at : IsolatedHostsFilter JsonFilterDifferentHostFilter /SameHostFilter Razique
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 19 juin 2012 à 10:54, Neelak
Even simpler yesThanks
Nuage & Co - Razique Mahroua razique.mahr...@gmail.com
Le 19 juin 2012 à 11:00, heut2008 a écrit :you should use admin credentials ,then run instances by adding anoption --force_hosts=node1 to nova boot .2012/6/19 Neelakantam Gaddam :Hi All,Nova s
Mark McLoughlin wrote:
> One question I had on that is re:
>
> the ability to release a client library outside of the core project
> release cycle (requests have been coming in to our release manager for
> this)
>
> Who were these request from and why? That would help understand what
> we'
On the Project & release status meeting on today:
Just two weeks left before Folsom-2 milestone-proposed branch is cut !
Time to readjust objectives and check that the essential stuff (think:
Cinder split) is covered.
Feel free to add extra topics to the agenda:
[1] http://wiki.openstack.org/Meet
Hello,
As part of the ceilometer project¹, we're working on usage data
retrieval from various OpenStack components. One of them is Glance.
We're targeting Folsom for the first release, therefore it seems
important for both projects to be able to work together, this is why
we're bringing ceilometer
Brian, Jay,
I'll give you a chance to reply to Julien first, but
I have a follow on query...
It doesn't seem like right now Glance produces enough records for full
metering of operations. Eg if you want to charge a specific user for
every successful image upload/image download this information d
On Tue, 2012-06-19 at 11:25 +0200, Thierry Carrez wrote:
> Mark McLoughlin wrote:
> > One question I had on that is re:
> >
> > the ability to release a client library outside of the core project
> > release cycle (requests have been coming in to our release manager for
> > this)
> >
> > W
Mark McLoughlin wrote:
>> Originally the client library projects were independent and were
>> released by their author to PyPI. People built their tooling and
>> automation
>
> Interested in specific examples ...
Most developers apparently pull their libraries from PyPI. It's a bit
strange for pe
On Tue, 2012-06-19 at 16:48 +0200, Thierry Carrez wrote:
> Mark McLoughlin wrote:
[..]
> >> However they also inherited the release scheme of the server project
> >> (new version every 6 months), which was (or was not) synced to PyPI
> >> depending of who was owning the PyPI project. More confusion
The swift probetests are broken:
https://bugs.launchpad.net/swift/+bug/1014931
Does the swift team intend to maintain probetests going forward? Given how
broken they are at present (bad imports, failures even when imports are fixed),
it would appear that probetests are not gating commits. Tha
On 06/19/2012 11:10 AM, Maru Newby wrote:
The swift probetests are broken:
https://bugs.launchpad.net/swift/+bug/1014931
Does the swift team intend to maintain probetests going forward? Given how
broken they are at present (bad imports, failures even when imports are fixed),
it would appear
Hi!
Unfortunately, nova, keystone, and glance clients are very inconsistent. A
lot of code is copied between all these clients instead of moving it to a
common library. The code was edited without synchronization between
clients, so, they have different behaviour:
- all client constructors use
Alexey -
where's the library of common that you've put together? Is it committed to
openstack-common? somewhere else?
-joe
On Jun 19, 2012, at 9:43 AM, Alexey Ababilov wrote:
> Unfortunately, nova, keystone, and glance clients are very inconsistent. A
> lot of code is copied between all these
Did you see:
https://github.com/openstack/python-openstackclient
Also, keep in mind that some of the ways the existing Glance client (and
Swift client FTM) work is due to lack of support in httplib2 for
chunked-transfer encoding.
Best,
-jay
On 06/19/2012 12:43 PM, Alexey Ababilov wrote:
Hi
Hi Ross,
In the process of diagnosing this, but I'm seeing this sporadically when
running Tempest against a devstack install. I'll try to pinpoint the
issue later today and post back my findings.
Best,
-jay
p.s. Sorry for top-posting.
On 06/18/2012 06:03 PM, Lillie Ross-CDSR11 wrote:
I'm r
Hi!
On 06/19/2012 09:43 AM, Alexey Ababilov wrote:
> Hi!
>
> Unfortunately, nova, keystone, and glance clients are very inconsistent.
> A lot of code is copied between all these clients instead of moving it
> to a common library. The code was edited without synchronization between
> clients, so,
Wrong list, rerouting the message to the appropriate one.
Please join the team and subscribe to the list on
https://launchpad.net/~openstack
/stef
On 06/19/2012 07:30 AM, badis hammi wrote:
> Hi friends,
> I'm new on this mailing list, I just begin with openstack and I wish to
> know if it exis
Hi Julien and Stuart! Comments inline...
On 06/19/2012 07:12 AM, stuart.mcla...@hp.com wrote:
Brian, Jay,
I'll give you a chance to reply to Julien first, but
I have a follow on query...
It doesn't seem like right now Glance produces enough records for full
metering of operations. Eg if you wa
Any clue on this guys?
On Mon, Jun 18, 2012 at 7:08 PM, Sajith Kariyawasam wrote:
> Hi all,
>
> I have Openstack Essex version installed and I have created several
> instances based on an Ubuntu-12.04 UEC image in Openstack and those are up
> and running.
>
> When I'm trying to terminate an insta
Hi everyone,
perhaps someone can shed some light on a floating IP issue.
I have 2 nova-compute nodes (call them alice and bob), one of them
(alice) is also running nova-network. bob uses alice as its
--metadata_host and --network_host.
I assign a floating IP to a guest running on bob. Expectedly
https://github.com/cloudscaling/tarkin
This is a very minimal test set that supports pinging vms after launching
them.
Nothing crazy.
-Matt
On Mon, Jun 18, 2012 at 6:37 AM, Jay Pipes wrote:
> On 06/14/2012 05:26 AM, Neelakantam Gaddam wrote:
>
>> Hi All,
>>
>> Recently I came across the tool
Hello Friends,
I have just started using Openstack. I am trying to make a web based
application for Openstack swift. I am using the Django and python for my
application. Could you please provide me few examples how to send the
command to swift server using python. I am able to get the auth toke
I'm going to top-post, because there is a whole other thing which is not
a response to points below. Basically, this is yet-another-instance of
two competing and partially contradictory sets of use cases and usage
patterns that we're trying to find the right compromise for.
Tying client libs to se
Some links to show you:
https://github.com/openstack/horizon/blob/7b565fc9839833b4b99b1fc3b02269b79071af3e/horizon/api/swift.py
https://github.com/openstack/horizon/blob/f6f2a91e14f6bdd4e1a87e31a1d6923127afee1b/horizon/dashboards/nova/containers/views.py
Best,
-jay
On 06/19/2012 02:04 PM, Yoge
Hi Mark,
I forgot to grab the blueprint but I finally got around to start working on
this. I'll hopefully have something to put up for review next week.
This version just support's basic GET/POST ops to retrieve the rings or to
view/alter/add devices to the ring in bulk.
Having someone else a
Hi Florian,
For my own setup, I wanted to achieve highly-available network, and avoid
the loss of the gateway of every instances running if nova-network falls
down. I couldn't afford 2 dedicated nodes to put nova-network itself in an
highly available state. Now if I loose a nova-network on a compu
cc'ing Vish on this, as this is now occurring on every single devstack +
Tempest run, for multiple servers.
Vish, I am seeing the exact same issue as shown below. Instances end up
in ERROR state and looking into the nova-network log, I find *no* errors
at all, and yet looking at the nova-compu
Alright. Is this something you're more or less done with and are just
cleaning up or have you just started? I've got my guys reading up on swift
and are about ready to dive in with the coding, so if you're more or less
done I'll find another project for them to work on. If you're just started
(o
On Jun 19, 2012, at 10:52 AM, Florian Haas wrote:
> Hi everyone,
>
> perhaps someone can shed some light on a floating IP issue.
>
> I have 2 nova-compute nodes (call them alice and bob), one of them
> (alice) is also running nova-network. bob uses alice as its
> --metadata_host and --network_h
This seems like a likely culprit.
Vish
On Jun 19, 2012, at 12:03 PM, Jay Pipes wrote:
> cc'ing Vish on this, as this is now occurring on every single devstack +
> Tempest run, for multiple servers.
>
> Vish, I am seeing the exact same issue as shown below. Instances end up in
> ERROR state an
It looks like Florian (at Rackspace) is working on that blueprint. He just
assigned it to himself.
I'm happy to hear that you have some extra devs for swift work. I'd love to
help coordinate some swift goals with you.
Off the top of my head, here are a few things that could be worked on:
1) Ha
Sorry, paste fail on the last message.
This seems like a likely culprit:
https://review.openstack.org/#/c/8339/
I'm guessing it only happens on concurrent builds? We probably need a
synchronized somewhere.
Vish
On Jun 19, 2012, at 12:03 PM, Jay Pipes wrote:
> cc'ing Vish on this, as this is
I just need to clean it up at this point (mainly the rebalance). Since the
rebalance (i.e. swift-ring-builder rebalance) can take minutes to complete when
you have lots of devices I need to move it off to a background task.
--
Florian Hines | @pandemicsyn
http://about.me/pandemicsyn
On Tuesd
That's looking pretty good, Sascha. May I suggest:
1. Instead of using the temporary lockfile, let's actually move slightly back
towards your original approach and check for the existence of a known secret
key file (added to .gitignore of course) which the get_secret_key function can
check for.
Hi Jay,
Thanks a lot for quick response. This was little helpful. I need how to send
the parameters to the swift server by making the connection. I think that
task is happening in inside the below code. Could you please tell me what is
happening in cloudfiles.get_connection method
def swift_api(
Vish, Jay,
OK, this looks promising. A couple of questions…
I'm seeing this RPC timeout on the Essex 2012.1 packages released with Ubuntu
12.04. I'm assuming these packages are affected by this bug?
Why would something this fundamental not show up during Essex RC.X testing?
How best to 'fix'
On 06/19/2012 03:13 PM, Vishvananda Ishaya wrote:
Sorry, paste fail on the last message.
This seems like a likely culprit:
https://review.openstack.org/#/c/8339/
I'm guessing it only happens on concurrent builds? We probably need a
synchronized somewhere.
I notice the the RPC calls to the ne
On 6/19/12 12:13 PM, John Dickinson wrote:
It looks like Florian (at Rackspace) is working on that blueprint. He just
assigned it to himself.
I'm happy to hear that you have some extra devs for swift work. I'd love to
help coordinate some swift goals with you.
Off the top of my head, here are
For those of you that don't know Cinder is the new project intended to
separate block storage out of Nova and provide it via it's own
service. The goal is to have a functional replacement for
Nova-Volumes by Folsom 2 (don't worry, you'll be able to select which
service to use). So far things have
Nice work.
When you've got the rest of the API bits ironed out (particularly
attach/detach) I'll help work on making sure Horizon is fully functional there.
Note that there's also an F3 Horizon blueprint for splitting volumes into its
own optional panel:
https://blueprints.launchpad.net/horizo
On 06/19/2012 10:52 AM, Florian Haas wrote:
Hi everyone,
perhaps someone can shed some light on a floating IP issue.
I have 2 nova-compute nodes (call them alice and bob), one of them
(alice) is also running nova-network. bob uses alice as its
--metadata_host and --network_host.
I assign a flo
On Tue, Jun 19, 2012 at 3:29 PM, Gabriel Hurley
wrote:
> Nice work.
>
> When you've got the rest of the API bits ironed out (particularly
> attach/detach) I'll help work on making sure Horizon is fully functional
> there. Note that there's also an F3 Horizon blueprint for splitting volumes
> in
I attempted to attach a volume to a running instance, but later
deleted the instance, leaving the volume stuck in the "attaching"
state:
# nova volume-list
++---+--+--+-+-+
| ID | Status | Display Name | Size | Volume Type | Attached to
Hi All,
I am trying multi node setup using openstack and quantum using devstack. My
understanding is that for every tenant, there is a gateway interface
created in the physical host and these will act as gateways for the
tenants. Is it possible to configure a VM as a gateway/router for a tenant
an
On Tue, Jun 19, 2012 at 7:40 PM, Lars Kellogg-Stedman
wrote:
> I attempted to attach a volume to a running instance, but later
> deleted the instance, leaving the volume stuck in the "attaching"
> state:
>
> # nova volume-list
> ++---+--+--+-+-
Hi all,
We have been having some issues in terminating LXC instances in Openstack
Nova, and found that the above mentioned bug [1] is already reported, and
according to [2] it is "high" and "confirmed".
We would like to know are there any plans to fix this issue immediately ?
or is there any work
Hi all,
I have implemented three more classes in Ceilometer plug-in module.
Added those classes in libvirt.py file in compute.
The classes which I have added are counters to find out the following:
1. Number of CPUs used
2. Memory used
3. Maximum memory used
I am also ready wi
When I tried this on post-essex release code, I got :
error: unrecognized arguments: --force_hosts=
Try --hint force_hosts= instead
-Mandar
-Original Message-
From: openstack-bounces+mandar.vaze=nttdata@lists.launchpad.net
[mailto:openstack-bounces+mandar.vaze=nttdata@li
Hi Mandar,
Thanks for your help.
This command is working for me.
Regards
Neelakantam
On Wed, Jun 20, 2012 at 11:37 AM, Vaze, Mandar wrote:
> When I tried this on post-essex release code, I got :
>error: unrecognized arguments: --force_hosts=
>
> Try --hint force_hosts= instead
>
> -Man
52 matches
Mail list logo