Re: [Openstack] project read-only role or create role with specific capabilities

2017-10-20 Thread Yaguang Tang 
you can archive what you want by modifying the policy.json of Nova and
other projects to define readonly role, and create that role in keystone,
then assign to users you want.

On Thu, Oct 19, 2017 at 3:15 PM, Chengwei Yang 
wrote:

> Hi list,
>
> As I understand, keystone only defined two roles:
>
>   - admin
>   - non-admin, but can be any role name you want, role1, role2, user,
> _member_, whatever
>
> say there are quite few people in the same project, so far, the users
> assigned with the same role has exactly the same right to a project.
>
> Is it possible to create a role with read-only capabilities with all
> resources in a project?
>
> If so, any hints?
>
> In addition, I'd like to create a role which isn't admin but can manage
> projects(create project, delete his project, manage project members and
> etc.)
>
> thanks in advance!
>
> --
> Thanks,
> Chengwei
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
>


-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [OpenStack] Can Mitaka RamFilter support free hugepages?

2017-09-08 Thread Yaguang Tang 
On Thu, Sep 7, 2017 at 4:05 PM, Sahid Orentino Ferdjaoui <
sferd...@redhat.com> wrote:

> On Wed, Sep 06, 2017 at 11:57:25PM -0400, Jay Pipes wrote:
> > Sahid, Stephen, what are your thoughts on this?
> >
> > On 09/06/2017 10:17 PM, Yaguang Tang wrote:
> > > I think the fact that RamFilter can't deal with huge pages is a bug ,
> > > duo to this limit, we have to set a balance  between normal memory and
> > > huge pages to use RamFilter and NUMATopologyFilter. what do you think
> > > Jay?
>
> Huge Pages has been built on top of the NUMA Topology
> implementation. You have to consider isolate all hosts which are going
> to handle NUMA instances to a specific host aggregate.
>
> We don't want RAMFilter to handle any NUMA related feature (in Nova
> world: hugepages, pinning, realtime...) but we don't want it blocking
> scheduling and that should not be the case.
>
> I'm surprised to see this bug I think libvirt is reporting the total
> amount of physical RAM available on the host and that is not depending
> of the size of the pages.
>
> So If that is true libvirt is reporting only the amount of small pages
> memory available we will probably have to fix that point instead of
> the RAMFilter.
>

 If we fix  it this way, the issue still exists, as long as user use
RamFilter and NUMATopologyFilter toghther.  Libvirt reports total memory
which contains huge pages
but normal instance can't use.

>
> That because we don't want to add "hack" on all filters to just pass
> when instances provide NUMA Topology constraints and we can't
> configure the scheduler to use specific filters per aggregate.
>

How about fixing RamFilter to just pass if the instance extra specs
specifies huge pages ?



>
> s.
>
> > >
> > > On Wed, Sep 6, 2017 at 9:22 PM, Jay Pipes  > > <mailto:jaypi...@gmail.com>> wrote:
> > >
> > > On 09/06/2017 01:21 AM, Weichih Lu wrote:
> > >
> > > Thanks for your response.
> > >
> > > Is this mean if I want to create an instance with flavor: 16G
> > > memory (hw:mem_page_size=large), I need to preserve memory more
> > > than 16GB ?
> > > This instance consume hugepages resource.
> > >
> > >
> > > You need to reserve fewer 1GB huge pages than 50 if you want to
> > > launch a 16GB instance on a host with 64GB of RAM. Try reserving 32
> > > 1GB huge pages.
> > >
> > > Best,
> > > -jay
> > >
> > > 2017-09-06 1:47 GMT+08:00 Jay Pipes  > > <mailto:jaypi...@gmail.com> <mailto:jaypi...@gmail.com
> > > <mailto:jaypi...@gmail.com>>>:
> > >
> > >
> > >  Please remember to add a topic [nova] marker to your
> > > subject line.
> > >  Answer below.
> > >
> > >  On 09/05/2017 04:45 AM, Weichih Lu wrote:
> > >
> > >  Dear all,
> > >
> > >  I have a compute node with 64GB ram. And I set 50
> > > hugepages wiht
> > >  1GB hugepage size. I used command "free", it shows
> free
> > > memory
> > >  is about 12GB. And free hugepages is 50.
> > >
> > >
> > >  Correct. By assigning hugepages, you use the memory
> > > allocated to the
> > >  hugepages.
> > >
> > >  Then I launch an instance with 16GB memory, set flavor
> > > tag :
> > >  hw:mem_page_size=large. It show Error: No valid host
> > > was found.
> > >  There are not enough hosts available.
> > >
> > >
> > >  Right, because you have only 12G of RAM available after
> > >  creating/allocating 50G out of your 64G.
> > >
> > >  Huge pages are entirely separate from the normal memory
> that a
> > >  flavor consumes. The 16GB memory in your flavor is RAM
> > > consumed on
> > >  the host. The huge pages are individual things that are
> > > consumed by
> > >  the NUMA topology that your instance will take. RAM !=
> huge
> > > pages.
> > >  Totally different things.
> > >
> > >And I check nova-scheduler log. My
> > >
> > >

Re: [Openstack] [OpenStack] Can Mitaka RamFilter support free hugepages?

2017-09-06 Thread Yaguang Tang 
I think the fact that RamFilter can't deal with huge pages is a bug , duo
to this limit, we have to set a balance  between normal memory and huge
pages to use RamFilter and NUMATopologyFilter. what do you think Jay?


On Wed, Sep 6, 2017 at 9:22 PM, Jay Pipes  wrote:

> On 09/06/2017 01:21 AM, Weichih Lu wrote:
>
>> Thanks for your response.
>>
>> Is this mean if I want to create an instance with flavor: 16G memory
>> (hw:mem_page_size=large), I need to preserve memory more than 16GB ?
>> This instance consume hugepages resource.
>>
>
> You need to reserve fewer 1GB huge pages than 50 if you want to launch a
> 16GB instance on a host with 64GB of RAM. Try reserving 32 1GB huge pages.
>
> Best,
> -jay
>
> 2017-09-06 1:47 GMT+08:00 Jay Pipes > jaypi...@gmail.com>>:
>>
>>
>> Please remember to add a topic [nova] marker to your subject line.
>> Answer below.
>>
>> On 09/05/2017 04:45 AM, Weichih Lu wrote:
>>
>> Dear all,
>>
>> I have a compute node with 64GB ram. And I set 50 hugepages wiht
>> 1GB hugepage size. I used command "free", it shows free memory
>> is about 12GB. And free hugepages is 50.
>>
>>
>> Correct. By assigning hugepages, you use the memory allocated to the
>> hugepages.
>>
>> Then I launch an instance with 16GB memory, set flavor tag :
>> hw:mem_page_size=large. It show Error: No valid host was found.
>> There are not enough hosts available.
>>
>>
>> Right, because you have only 12G of RAM available after
>> creating/allocating 50G out of your 64G.
>>
>> Huge pages are entirely separate from the normal memory that a
>> flavor consumes. The 16GB memory in your flavor is RAM consumed on
>> the host. The huge pages are individual things that are consumed by
>> the NUMA topology that your instance will take. RAM != huge pages.
>> Totally different things.
>>
>>   And I check nova-scheduler log. My
>>
>> compute is removed by RamFilter. I can launch an instance with
>> 8GB memory successfully, or I can launch an instance with 16GB
>> memory sucessfully by remove RamFilter.
>>
>>
>> That's because RamFilter doesn't deal with huge pages. Because huge
>> pages are a different resource than memory. The page itself is the
>> resource.
>>
>> The NUMATopologyFilter is the scheduler filter that evaluates the
>> huge page resources on a compute host and determines if the there
>> are enough *pages* available for the instance. Note that I say
>> *pages* because the unit of resource consumption for huge pages is
>> not MB of RAM. It's a single memory page.
>>
>> Please read this excellent article by Steve Gordon for information
>> on what NUMA and huge pages are and how to use them in Nova:
>>
>> http://redhatstackblog.redhat.com/2015/09/15/driving-in-the-
>> fast-lane-huge-page-support-in-openstack-compute/
>> > the-fast-lane-huge-page-support-in-openstack-compute/>
>>
>> Best,
>> -jay
>>
>> Does RamFilter only check free memory but not free hugepages?
>> How can I solve this problem?
>>
>> I use openstack mitaka version.
>>
>> thanks
>>
>> WeiChih, Lu.
>>
>> Best Regards.
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> 
>> Post to : openstack@lists.openstack.org
>> 
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> 
>>
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> 
>> Post to : openstack@lists.openstack.org
>> 
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> 
>>
>>
>>
>>
>> ___
>> Mailing list: http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe : http://lists.openstack.org/cgi
>> -bin/mailman/listinfo/openstack
>>
>>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstac
> k
>



-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/open

Re: [Openstack] Why the gnocchi resource list only have generic and image not cpu, memory etc

2017-08-25 Thread Yaguang Tang 
Can you make sure that you have the instance related resource type created
already, run "gnocchi resource-type list"

On Fri, Aug 18, 2017 at 9:42 PM, ? ?  wrote:

> Thank you for viewing my post. I hope you can help me.
>
>
>
> This also post on : https://stackoverflow.com/questions/45727824/why-the-
> gnocchi-resource-list-only-have-generic-and-image-not-cpu-memory-etc
>
>
>
> I deployed the ceilometer service on Ocata and use gnocchi as it is
> database backend. I need to monitor some indexs of OpenStack such as cpu,
> memory etc. And I had launch an instances, but the ceilometer-collector's
> log show it not exist.
>
> # openstack server list
>
> +--+---++-++
>
> | ID   | Name  | Status | 
> Networks| Image Name |
>
> +--+---++-++
>
> | ac0f56a0-7de1-4433-a682-cb50edd34ff8 | provider-instance | ACTIVE | 
> provider=192.168.32.206 | cirros |
>
> +--+---++-++
>
> When i list the gnocchi resource :
>
> # gnocchi resource list
>
> Its output only one resource and that type is generic and image:
>
> # gnocchi resource list
>
> +--+-+--+-+--+--+--+--+--+-+
>
> | id   | type| project_id   | user_id | 
> original_resource_id | started_at   | ended_at | revision_start   | 
> revision_end | creator |
>
> +--+-+--+-+--+--+--+--+--+-+
>
> | 83746b69-87e8-4e | generic | None | None| 
> 83746b69-87e8-4ee2   | 2017-08-17T11:39 | None | 2017-08-17T11:39 | None  
>| :   |
>
> | e2-b9af- | |  | | 
> -b9af-39769cc32b75   | :46.861664+00:00 |  | :46.861693+00:00 |   
>| |
>
> | 39769cc32b75 | |  | |   
>|  |  |  |  |  
>|
>
> | 078094a0-d02d-   | image   | c9e5e8bd3e0f4303 | None| 
> 078094a0-d02d-4e55   | 2017-08-17T12:05 | None | 2017-08-17T12:05 | None  
>| aab0cfe190814e00bcd |
>
> | 4e55-a8be-   | | 93163890a81cbeca | | 
> -a8be-4cd897b64a2b   | :53.440542+00:00 |  | :53.440708+00:00 |   
>| 8cf65c3462f58:ff2d0 |
>
> | 4cd897b64a2b | |  | |   
>|  |  |  |  | 
> f401c5e4b87935548b8 |
>
> |  | |  | |   
>|  |  |  |  | c3a01ad2 
>|
>
> +--+-+--+-+--+--+--+--+--+-+
>
> There are some logs and configurations：
>
> gnocchi-api -p 8041 &>> /var/log/gnocchi/gnocchi-uwsgi.log
>
> 192.168.32.134 - - [18/Aug/2017 09:43:00] "GET /v1/capabilities/ HTTP/1.1" 
> 200 1030
>
> 192.168.32.134 - - [18/Aug/2017 09:43:22] "GET /v1/capabilities/ HTTP/1.1" 
> 200 1030
>
> 192.168.32.134 - - [18/Aug/2017 09:43:36] "POST 
> /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1" 400 217
>
> 192.168.32.134 - - [18/Aug/2017 09:43:36] "POST 
> /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1" 400 217
>
> 192.168.32.134 - - [18/Aug/2017 09:43:36] "POST 
> /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1" 400 217
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST 
> /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1" 400 217
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST 
> /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1" 202 4
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST 
> /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1" 202 4
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST 
> /v1/batch/resources/metrics/measures?create_metrics=True HTTP/1.1" 400 217
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST /v1/resource/instance 
> HTTP/1.1" 400 117
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST /v1/resource/instance 
> HTTP/1.1" 400 117
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST /v1/resource/instance 
> HTTP/1.1" 400 117
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "POST /v1/resource/instance 
> HTTP/1.1" 400 117
>
> 192.168.32.134 - - [18/Aug/2017 09:43:37] "PATCH 
> /v1/resource/image/078094a0

Re: [Openstack] Guest agent and fsfreeze

2015-01-03 Thread Yaguang Tang 
This feature is being added during Kilo,
https://blueprints.launchpad.net/nova/+spec/quiesced-image-snapshots-with-qemu-guest-agent,
so if you want to test it, it's better to use devstack with trunk,
there are some requirements:
1. libvirt >=1.2.5
2. os_require_quiesce=yes need to be set as image property

Note that so far only support instances booted from glance images,
instances booted from
volume for this  feature is working in progress
https://review.openstack.org/#/c/138795/.

Related wiki
https://wiki.openstack.org/wiki/Cinder/QuiescedSnapshotWithQemuGuestAgent




On Sat, Jan 3, 2015 at 4:30 AM, Tim Bell  wrote:

>
>
> I'm trying to get the guest agent working on OpenStack.
>
>
>
> I have enabled the guest agent using the property
>
>
>
> | Property 'hw_qemu_guest_agent' | yes |
>
>
>
> The VM has the qemu guest agent installed
>
>
>
> $ rpm -qa | grep guest
>
> qemu-guest-agent-1.5.3-60.el7_0.11.x86_64
>
>
>
> The service has been started
>
>
>
> /bin/systemctl status qemu-guest-agent.service
>
> qemu-guest-agent.service - QEMU Guest Agent Loaded: loaded
> (/usr/lib/systemd/system/qemu-guest-agent.service; static)
>
> Active: active (running) since Sun 2014-12-21 17:45:32 CET; 18h ago
>
> Main PID: 1066 (qemu-ga) CGroup: /system.slice/qemu-guest-agent.service
> └─1066 /usr/bin/qemu-ga --method=virtio-serial
> --path=/dev/virtio-ports/org.qemu.guest_agent.0 --bla...
>
> Dec 21 17:45:32 timhwag144 systemd[1]: Started QEMU Guest Agent.
>
>
>
> However, when I run the nova image-create command, I do not get any entry
> in /var/log/qemu-ga to show that fsfreeze has been run.
>
>
>
> Any suggestions ? I could not find any documentation on how to do fsfreeze
> with QEMU GA other than the blueprints implementing the function.
>
>
>
> Tim
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Scheduled Backup (was Openstack capabilities)

2014-12-28 Thread Yaguang Tang 
On Wed, Dec 24, 2014 at 2:20 AM, Tim Bell  wrote:

>
>
> There is a need for an end user service for backup/snapshot on a schedule.
> Raksha (https://wiki.openstack.org/wiki/Raksha) was close but does not
> seem to be actively developed at the moment. Extensions for remote
> replication on schedule would be really welcome.
>

   There is a project called Mistral (
https://wiki.openstack.org/wiki/Mistral
<https://wiki.openstack.org/wiki/Mistral>) which is a task management
service, designed for OpenStack user tasks.
   It aims at providing a widely used cloud cron service.

>
>
> It is not clear to me how the standard user arranges a reasonable backup
> strategy for their VM currently on OpenStack ?
>
>
>
> While there are some applications which can be re-created from scratch
> faster than from backup, the typical CERN test/dev instance is where people
> try out ideas before setting things up in Puppet or with external volumes.
> Explaining that the VM is lost is not an easy discussion.
>
>
>
> It can all be scripted… can we arrange that this this requires a
> relatively limited effort to script ? Passwords, expiration of old images
> and replication are not trivial problems to solve for the average end user.
>
>
>
> Tim
>
>
>
> *From:* Yaguang Tang [mailto:heut2...@gmail.com]
> *Sent:* 23 December 2014 10:35
> *To:* Erik McCormick
> *Cc:* openstack@lists.openstack.org
> *Subject:* Re: [Openstack] Openstack capabilities
>
>…
>
> 14.Supports backup manager
>
>
> The snapshot operation and daily/weekly/hourly backup operations are
> currently supported via OpenStack Nova's API. However, if you're looking
> for some Windows GUI that does backups, that isn't something that OpenStack
> is about to provide.
>
>
>
>   Yeah we do have API support for instance backup periodically , but
> AFAIK this feature doesn't work at all, there isn't a periodic worker doing
> that, and
>
>instance periodic backup info isn't stored anywhere, I have written
> a patch to implement that for a customer before, if this is a common
> feature request,  I'd like to discuss in the openstack-dev ML and
> contribute it to upstream.
>
>
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] failed live migration openstack juno el7 using giant

2014-12-23 Thread Yaguang Tang 
Hi samuel,

Sometimes live migration couldn't be rollback when error occurs, so the
destination instance disk path remains there, you have to manually resolve
this by delete that directory manually, and please try again.

On Tue, Dec 23, 2014 at 11:24 PM, samuel  wrote:

> Dear list,
>
> We've recently faced an issue regarding live migration on a Juno openstack
> installation using a ceph giant shared storage.
>
> The error that appear is
>
> DestinationDiskExists: The supplied disk path
> (/var/lib/nova/instances/instance-id-hidden) already exists, it is expected
> not to exist.
>
> I've located several entries, such as:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1150856
> https://review.openstack.org/#/c/111082/
>
> But the error still persist and some of the patches have already been
> included. The current version is the following:
>
> Name: openstack-nova-compute
> Version : 2014.2.1
> Release : 1.el7.centos
>
>
> It looks like there's an issue regarding shared storage and the
> assumptions of this path.
>
> Can anyone provide information about this issue?
>
> Regards,
> Samuel.
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Openstack capabilities

2014-12-23 Thread Yaguang Tang 
On Tue, Dec 23, 2014 at 6:14 AM, Erik McCormick 
wrote:

> I have a slightly different take on some of this:
>
> On Mon, Dec 22, 2014 at 11:52 AM, Jay Pipes  wrote:
>>
>> On 12/22/2014 11:20 AM, Eriane Leobrera wrote:
>>
>>> Hi OpenStack,
>>>
>>> I would really appreciate if anyone can assist me on my dilemma. Below
>>> are the capabilities I am looking for. We are on the process of deciding
>>> between OpenStack vs CloudStack. Capabilities are much more important
>>> for us, integrated and having everything automated.
>>>
>>> Here are the list below:
>>>
>>
>> I've tried to give you honest answers from the OpenStack roadmap and
>> currently-supported perspective below.
>>
>>  1.Integration with CRM 2013 (service tickets, lead/opportunity,
>>> contact/account and billing system).
>>>
>>
>> Not supported now. Not likely to ever be supported by OpenStack, too much
>> of a custom feature.
>>
>
> Agreed, but you can do tie in via the billing system potentially so as to
> map tickets to tenants. This isn't an Openstack feature, but it is possible
> with the correct tooling.
>
>>
>>  2.Integration with payment gateway (Moneris)
>>>
>>
>> Not supported now. Not likely to ever be supported by OpenStack, too much
>> of a custom feature.
>>
>
> Again, this is possible via 3rd party tooling integrating with your
> billing system, but not an Openstack feature.
>
>>
>>  3.PCI Compliant solution
>>>
>>
>> This is a giant rabbithole.
>>
>
> It is a giant rabbithole, but there's nothing in Openstack that is
> inherently *not* compliant. Having been through a number of these, you can
> achieve all of the audit requirements by properly configuring your cloud
> the way you would any other system.
>
>
>>
>>  4.Audit trail enabled on all interactions (i.e server shutdown etc.)
>>>
>>
>> OpenStack currently supports notification queues that can be used to
>> provide audit capabilities.
>>
>>  5.Support buying a new VM, signing up, auto charging them by credit card
>>> verification and auto provisioning VMs.
>>>
>>
>> Not supported now. Not likely to ever be supported by OpenStack, too much
>> of a custom feature for the user interface, which is something that
>> OpenStack's upstream UI (Horizon) is unlikely to develop.
>>
>> Again, this is a 3rd party problem. Openstack provides all the hooks that
> you need to tie in something like Velvica to manage users, signup, billing
> integration, etc. Usage data is provided by Ceilometer. Most of these
> systems relay out to horizon, but there are a few that replace the
> dashboard entirely. This is becoming a much richer space with more players
> all the time.
>
>  6.Upgrade existing VMs with ability to reboot VM to have resources added
>>>
>>
>> Currently supported. This is the resize/migrate operation in nova.
>>
>>  7.Cancel VM which stops billing and scheduling for VM to be removed for
>>> x days later
>>>
>>
>> Not currently supported. Possibly supported some time in the future if we
>> decide it's worthwhile to put time-based constraints and reservations into
>> the scheduler.
>>
>> See #5
>
>
>>  8.Support for pay by the minute billing
>>>
>>
>> OpenStack does not ship a billing solution. This is something that is the
>> responsibility of the operator, since it's a *very* custom feature and
>> almost always involves proprietary code linking.
>>
>>  9.Support for multiple data centre locations
>>>
>>
>> This is currently supported.
>>
>>  Specifically look at documentation around Regions.
>
>
>> 10.Supports a DNS Manager
>>>
>>
>> This is currently supported with the Designate component.
>>
>>  11.Ability to do a hard shutdown on VM
>>>
>>
>> This is currently supported.
>>
>>  12.Ability to have console level access
>>>
>>
>> This is currently supported.
>>
>>  13.Spin up new instance which wipes old instance and ability to reinstall
>>>
>>
>> This doesn't really make any sense. This isn't cloud. This is bare-metal
>> hosting you are describing.
>>
>> OpenStack's VMs are hosted in the cloud -- i.e. virtualized. When you
>> terminate a VM, you lose the data on the VM's ephemeral storage, which is
>> why for data that you need to keep around, you use volumes (block storage).
>>
>>  14.Supports backup manager
>>>
>>
>> The snapshot operation and daily/weekly/hourly backup operations are
>> currently supported via OpenStack Nova's API. However, if you're looking
>> for some Windows GUI that does backups, that isn't something that OpenStack
>> is about to provide.
>>
>
  Yeah we do have API support for instance backup periodically , but
AFAIK this feature doesn't work at all, there isn't a periodic worker doing
that, and
   instance periodic backup info isn't stored anywhere, I have written
a patch to implement that for a customer before, if this is a common
feature request,  I'd like to discuss in the openstack-dev ML and
contribute it to upstream.

>
>>  15.Ability to change password for panel login via email or security
>>> questions etc.
>>>
>>
>> Changing passwords is cu

Re: [Openstack] [Junos][NOVA] - Error in nova-compute service

2014-11-11 Thread Yaguang Tang 
Hi sadia,

It seems that in your nova.conf  you set
my_ip = controller
which causes this issue, please use  my_ip = 192.168.1.6 and try to run
nova-compute again.

On Tue, Nov 11, 2014 at 4:31 PM, Sadia Bashir <11msccssbas...@seecs.edu.pk>
wrote:

> Hi everyone,
>
> I am installing Junos All-in-One on Ubuntu-14.04, Installed all services
> successfully as given in the openstack installation guide:
> http://docs.openstack.org/juno/install-guide/install/apt/content/ch_preface.html,
> but I am getting one weird error in nova-compute:
>
> Traceback (most recent call last):
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/conductor/manager.py", line$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> return getattr(target, method)(context, *args, **kwargs)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/base.py", line 155,$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> result = fn(cls, context, *args, **kwargs)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/service.py", line 1$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> return cls._from_db_object(context, cls(), db_service)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/service.py", line 7$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> service._do_compute_node(context, service, db_service)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/service.py", line 6$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> context, objects.ComputeNode(), db_compute)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/compute_node.py", l$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> compute[key] = db_compute[key]
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/base.py", line 474,$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> setattr(self, name, value)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/base.py", line 75, $
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> field_value = field.coerce(self, name, value)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/fields.py", line 18$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> return self._type.coerce(obj, attr, value)
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> File "/usr/lib/python2.7/dist-packages/nova/objects/fields.py", line 31$
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> raise ValueError(six.text_type(e))
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> 2014-11-11 13:16:22.349 30574 TRACE nova.openstack.common.threadgroup
> ValueError: failed to detect a valid IP address from u'controller'
>
> Here is /etc/hosts file:
>
> 127.0.0.1   localhost
> 127.0.1.1   icehouse-HP
> 192.168.1.6 controller
>
> # The following lines are desirable for IPv6 capable hosts
> ::1 ip6-localhost ip6-loopback
> fe00::0 ip6-localnet
> ff00::0 ip6-mcastprefix
> ff02::1 ip6-allnodes
> ff02::2 ip6-allrouters
>
> Moreover, all nova services except the compute service are up with nova
> service-list.
>
> Pls see nova.conf file attached.
>
> Reinstallation of nova-compute, dropping and creating nova Database, and
> recreating nova user didn't resolve this problem. I am not understanding
> what exactly is the source of this problem
>
> Please review nova.conf file and log I have attached/pasted here to
> identify the problem. Any help/guideline/solution will be appreciated to
> fix this bug.
>
> Thanks and Regards,
> --
> *Sadia Bashir*
>
>
>
> ___
> Mailing

[Openstack] console.log grows indefinitely issue

2014-10-08 Thread Yaguang Tang 
Hi all,

Here is a known issue for a long time
https://bugs.launchpad.net/nova/+bug/832507, vm console.log can grows
indefinitely if you are using kvm hypervisor,
this issue still remains to be fixed, before it get fixed in upstream, is
there any
workaround for this ? I think this could be an security/operator issue if
you are running an public cloud, compute node disk can be filled quickly
without limitation which could be kind of DoS.


-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] cinderclient - listing endpoints

2014-09-16 Thread Yaguang Tang 
Hi Michael,

Endpoints get managed by keystone,  when issue a token from keystone, it
will return a list of endpoints available to your requested user,  if you
are using v3 API, there is an option include_service_catalog which can be
used to omit catalog info.

On Tue, Sep 16, 2014 at 1:28 AM, Michael Hearn  wrote:

> Guys
>
> I see the cinderclient tool allows a non-privileged user the ability to
> list endpoints for all  services.
> Is there any reason not to update the cinder policy file to disable this
> behavior , and, can anyone tell me the policy that would need (adding)
> updating.
> I see no obvious policy in policy.json and the logs are not helpful.
>
> Many Thanks
> Mike.
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] iops limiting with OpenStack Nova using Ceph/Network Storage

2014-08-27 Thread Yaguang Tang 
CONF.libvirt.images_default_iops_second isn't in upstream yet,  anyway I
think this is definitely a bug and we should support set rate limit for rbd
disk backend.
I filed a bug here to track this issue.
https://bugs.launchpad.net/nova/+bug/1362129



On Wed, Aug 27, 2014 at 7:05 PM, Haomai Wang  wrote:

> Yes, it's possible just like a volume from Cinder. But it still exists
> some works todo. We need to pass iops/bw throttle value in via config
> or flavor metadata. If you want to get it as quick as possible, you
> can add some hack codes like this:
>
> tune_items = ['disk_read_bytes_sec', 'disk_read_iops_sec',
> 'disk_write_bytes_sec', 'disk_write_iops_sec',
> 'disk_total_bytes_sec', 'disk_total_iops_sec']
> # Note(yaguang): Currently, the only tuning available is Block I/O
> # throttling for qemu.
> if self.source_type in ['file', 'block']:
> for key, value in extra_specs.iteritems():
> scope = key.split(':')
> if len(scope) > 1 and scope[0] == 'quota':
> if scope[1] in tune_items:
> setattr(info, scope[1], value)
> +if not getattr(info, 'disk_total_bytes_sec'):
> +setattr(info, 'disk_total_bytes_sec',
> CONF.libvirt.images_default_bw_second)
> +if not getattr(info, 'disk_total_iops_sec'):
> +setattr(info, 'disk_total_iops_sec',
> CONF.libvirt.images_default_iops_second)
> return info
>
> On Wed, Aug 27, 2014 at 4:32 PM, Tyler Wilson 
> wrote:
> > Hey All,
> >
> > Is it possible to setup a iops/bytesps limitation within nova using
> libvirt
> > methods? I've found the following links but cant get it to work with my
> > environment;
> >
> > http://ceph.com/planet/openstack-ceph-rbd-and-qos/
> > https://wiki.openstack.org/wiki/InstanceResourceQuota
> >
> > I see in the commit code that it specifically mentions file and block
> with
> > no network in the code;
> >
> > tune_items = ['disk_read_bytes_sec', 'disk_read_iops_sec',
> > 'disk_write_bytes_sec', 'disk_write_iops_sec',
> > 'disk_total_bytes_sec', 'disk_total_iops_sec']
> > # Note(yaguang): Currently, the only tuning available is Block
> I/O
> > # throttling for qemu.
> > if self.source_type in ['file', 'block']:
> > for key, value in extra_specs.iteritems():
> > scope = key.split(':')
> > if len(scope) > 1 and scope[0] == 'quota':
> > if scope[1] in tune_items:
> > setattr(info, scope[1], value)
> > return info
> >
> > Is it possible to limit or establish QoS rules for network storage in
> nova
> > currently or only in cinder? My source protocol is rbd, qemu driver and
> raw
> > disk type.
> >
> > ___
> > Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> > Post to : openstack@lists.openstack.org
> > Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> >
>
>
>
> --
> Best Regards,
>
> Wheat
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>



-- 
Tang Yaguang
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] nova-compute unable to start

2014-08-18 Thread Yaguang Tang 
Hi Bill,

Could you please check whether libvirt daemon works well?


On Thu, Aug 14, 2014 at 6:52 PM, Bill WONG  wrote:

> Hi All,
>
> i installed the 3 nodes OpenStack with Ubuntu 14.04.1, i followed the
> document @ openstack official website, i installed everything, and it looks
> fine. but i don't know why nova-compute is unable to startup at Compute
> node. the log as below: please anyone can help with? thank you!
> (p.s. few weeks, before, i can installed and working without problem, but
> don't know why suddnely now it is not working, i am very sure, all steps
> and necessary packages have been installed and tried to re-install many
> times, but the result is the same.)
>
>  nova-compute.log ---
> 2014-08-14 15:09:10.474 13058 INFO nova.openstack.common.periodic_task [-]
> Skipping periodic task _periodic_update_dns because its interval is negative
> 2014-08-14 15:09:10.508 13058 INFO nova.virt.driver [-] Loading compute
> driver 'libvirt.LibvirtDriver'
> 2014-08-14 15:09:10.532 13058 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connected to AMQP server on controller:5672
> 2014-08-14 15:09:10.551 13058 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connected to AMQP server on controller:5672
> 2014-08-14 15:09:10.613 13058 AUDIT nova.service [-] Starting compute node
> (version 2014.1.2)
> 2014-08-14 15:10:10.678 13058 WARNING nova.virt.libvirt.driver
> [req-68c41414-06de-4cc2-9981-4caf14320716 None None] Cannot update service
> status on host: compute1,due to an unexpected exception.
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver Traceback
> (most recent call last):
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2834,
> in _set_host_enabled
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver service =
> service_obj.Service.get_by_compute_host(ctx, CONF.host)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/nova/objects/base.py", line 110, in
> wrapper
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver args,
> kwargs)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/nova/conductor/rpcapi.py", line 425, in
> object_class_action
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver
> objver=objver, args=args, kwargs=kwargs)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo/messaging/rpc/client.py", line 150,
> in call
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver
> wait_for_reply=True, timeout=timeout)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo/messaging/transport.py", line 90, in
> _send
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver
> timeout=timeout)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py",
> line 412, in send
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver return
> self._send(target, ctxt, message, wait_for_reply, timeout)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py",
> line 403, in _send
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver result =
> self._waiter.wait(msg_id, timeout)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py",
> line 267, in wait
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver reply,
> ending = self._poll_connection(msg_id, timeout)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver   File
> "/usr/lib/python2.7/dist-packages/oslo/messaging/_drivers/amqpdriver.py",
> line 217, in _poll_connection
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver % msg_id)
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver
> MessagingTimeout: Timed out waiting for a reply to message ID
> b881acc7092543a0affe821f34a7b531
> 2014-08-14 15:10:10.678 13058 TRACE nova.virt.libvirt.driver
> 2014-08-14 15:10:10.683 13058 WARNING nova.virt.libvirt.driver [-] URI
> qemu:///system does not support events: Cannot write data: Broken pipe
> 2014-08-14 15:10:10.687 13058 ERROR nova.openstack.common.threadgroup [-]
> internal error: client socket is closed
> 2014-08-14 15:10:10.687 13058 TRACE nova.openstack.common.threadgroup
> Traceback (most recent call last):
> 2014-08-14 15:10:10.687 13058 TRACE nova.openstack.common.threadgroup
> File
> "/usr/lib/python2.7/dist-packages/nova/openstack/common/threadgroup.py",
> line 117, in wait
> 2014-08-14 15:10:10.687 13058 TRACE nova.openstack.common.threadgroup
> x.wait()
> 2014-08-14 15:10:10.687 13058 TRACE nova.openstack.common.threadgroup
> File
>

Re: [Openstack] [Nova] Icehouse - Virtual Interface creation failed

2014-04-26 Thread Yaguang Tang 
The answer here may helps you  for the same issue
https://ask.openstack.org/en/question/26985/icehouse-virtual-interface-creation-failed/


2014-04-19 21:55 GMT+08:00 trinath.soman...@freescale.com <
trinath.soman...@freescale.com>:

>  Hi-
>
>
>
> I got this error when I launched an instance
>
>
>
> 2014-04-19 19:35:19.470 20217 INFO nova.virt.libvirt.driver
> [req-b061faf1-32bc-42d1-a1f4-822fcc9aaca5 3e7ba37aa6cf4472b823c8057a29c217
> 93a7bf9a8cb64c0da27486e722ce07c1] [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] Deleting instance files
> /var/lib/nova/instances/bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6
>
> 2014-04-19 19:35:19.472 20217 INFO nova.virt.libvirt.driver
> [req-b061faf1-32bc-42d1-a1f4-822fcc9aaca5 3e7ba37aa6cf4472b823c8057a29c217
> 93a7bf9a8cb64c0da27486e722ce07c1] [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] Deletion of
> /var/lib/nova/instances/bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6 complete
>
> 2014-04-19 19:35:19.623 20217 ERROR nova.compute.manager
> [req-b061faf1-32bc-42d1-a1f4-822fcc9aaca5 3e7ba37aa6cf4472b823c8057a29c217
> 93a7bf9a8cb64c0da27486e722ce07c1] [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] Instance failed to spawn
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] Traceback (most recent call last):
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6]   File
> "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1720, in
> _spawn
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] block_device_info)
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6]   File
> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 2253,
> in spawn
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] block_device_info)
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6]   File
> "/usr/lib/python2.7/dist-packages/nova/virt/libvirt/driver.py", line 3663,
> in _create_domain_and_network
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] raise
> exception.VirtualInterfaceCreateException()
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6] VirtualInterfaceCreateException:
> Virtual Interface creation failed
>
> 2014-04-19 19:35:19.623 20217 TRACE nova.compute.manager [instance:
> bf2d05ff-1de4-459b-8b18-3fc2a8ed44e6]
>
>
>
> Kindly help me resolve the issue.
>
>
>
> --
>
> Trinath Somanchi - B39208
>
> trinath.soman...@freescale.com | extn: 4048
>
>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang

Canonical Ltd. | www.ubuntu.com | www.canonical.com
Mobile:  +86 152 1094 6968
gpg key: 0x187F664F
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Question regarding Nova in Havana

2014-04-15 Thread Yaguang Tang 
Hi Prashant,

when the service starts, it checks if it has already registered in the
database, if not, it will update the db to create an item for itself. you
can see from the nova/service.py

149 def start(self):
150 verstr = version.version_string_with_package()
151 LOG.audit(_('Starting %(topic)s node (version %(version)s)'),
152   {'topic': self.topic, 'version': verstr})
153 self.basic_config_check()
154 self.manager.init_host()
155 self.model_disconnected = False
156 ctxt = context.get_admin_context()
157 try:
158 self.service_ref =
self.conductor_api.service_get_by_args(ctxt,
159 self.host, self.binary)
160 self.service_id = self.service_ref['id']
161 except exception.NotFound:
162 self.service_ref = self._create_service_ref(ctxt)

I think you need to add this logic to your fake nova-compute service.




2014-04-16 12:04 GMT+08:00 Prashant Upadhyaya <
prashant.upadhy...@aricent.com>:

>  Hi,
>
>
>
> I am writing a Compute Node Simulator.
>
> The idea is that I would write a piece of software using C which honors
> the RabbitMQ interface towards the Controller, but will not actually do the
> real thing – everything on the Compute Node will be simulated by my
> simulator software.
>
>
>
> The  problem I am facing, that I have not been able to get my simulated CN
> listed in the output of
>
> nova-manage service list
>
>
>
> I am on Havana, and my simulator is sending a periodic  ‘service_update’
> and ‘compute_node_update’ RPC messages to the ‘nova’ exchange and the
> ‘conductor’ routing key.
>
> I can manipulate the above messages at will to fool the controller.
>
> (I observe the messages from a real CN and take cues from there to
> construct a fake one from my simulator)
>
>
>
> Question is – what causes the controller to add a new Nova Compute in its
> database, is it the ‘service_update’ RPC or something else.
>
>
>
> Hopefully you can help me reverse engineer the interface.
>
>
>
> Regards
>
> -Prashant
>
>
>
>
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of
> this message. Aricent accepts no responsibility for loss or damage arising
> from the use of the information transmitted by this email including damage
> from virus."
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang

Canonical Ltd. | www.ubuntu.com | www.canonical.com
Mobile:  +86 152 1094 6968
gpg key: 0x187F664F
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Glance Image list not working after Keystone SSL setup

2014-04-14 Thread Yaguang Tang 
Devendra,

Please try add auth_version=2.0 to the keystone_authtoken section on both
nova and neutron conf file. there is a bug may affect you.
referred to
https://ask.openstack.org/en/question/8235/havana-neutron-unauthorized-authentication-required/


2014-04-14 22:35 GMT+08:00 Devendra Gupta :

> Thank you Yaguang.
>
> Now glance image-list is working fine with adding
> "insecure=True" to glance-api.conf and glance-register.conf below
> keystone_authtoken section. I'll also try the approach suggested by
> Rob for adding cafile path.
>
> I also set "insecure=True" for nova and neutron. Nova is working fine
> with SSL enabled keystone but neutron is still having weird issue. I
> am doing Google around it and I see lots of bugs related to the issue
> but nothing is clear if it's a bug or config issue, I am trying some
> workarounds but nothing seems working. When I try to do "neutron
> net-list", I can see error as "Authentication required"
>
> /etc/neutron/server.log shows following lines when net-list command is
> executed:
>
> 2014-04-15 03:50:34.947 24843 INFO urllib3.connectionpool [-] Starting
> new HTTPS connection (1): openstack-centos65
> 2014-04-15 03:50:35.045 24843 WARNING
> keystoneclient.middleware.auth_token [-] Verify error: Command
> 'openssl' returned non-zero exit status 4
> 2014-04-15 03:50:35.048 24843 WARNING
> keystoneclient.middleware.auth_token [-] Authorization failed for
> token 19ecd7820e37141d83f5ff7339da6656
> 2014-04-15 03:50:35.050 24843 INFO
> keystoneclient.middleware.auth_token [-] Invalid user token -
> rejecting request
>
> Neutron net-list --verbose output is attached. Please let me know your
> inputs.
>
> Regards,
> Devendra Gupta
>
>
> On Mon, Apr 14, 2014 at 11:27 AM, Yaguang Tang  wrote:
>
>> I think you should add insecure=True to glance-api.conf and
>> glance-register.conf below keystone_authtoken section.
>>
>>
>> 2014-04-14 12:45 GMT+08:00 Devendra Gupta :
>>
>> Ok Yelu, I am trying this, though glance image-list was working fine
>>> before configuring keystone to SSL. BTW please also see the SSL error I saw
>>> in glance api.log
>>>
>>> 2014-04-14 18:08:37.011 1989 INFO urllib3.connectionpool [-] Starting
>>> new HTTPS connection (1): openstack-centos65
>>> 2014-04-14 18:08:37.039 1989 WARNING
>>> keystoneclient.middleware.auth_token [-] Retrying on HTTP connection
>>> exception: [Errno 1] _ssl.c:492: error:14090086:SSL
>>> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
>>> 2014-04-14 18:08:39.041 1989 INFO urllib3.connectionpool [-] Starting
>>> new HTTPS connection (1): openstack-centos65
>>> 2014-04-14 18:08:39.069 1989 ERROR keystoneclient.middleware.auth_token
>>> [-] HTTP connection exception: [Errno 1] _ssl.c:492: error:14090086:SSL
>>> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
>>> 2014-04-14 18:08:39.069 1989 WARNING
>>> keystoneclient.middleware.auth_token [-] Authorization failed for token
>>> 123aa9518c869b95c2d75ab49f12c139
>>> 2014-04-14 18:08:39.070 1989 INFO keystoneclient.middleware.auth_token
>>> [-] Invalid user token - deferring reject downstream
>>>
>>> Regards,
>>> Devendra
>>>
>>> On Mon, Apr 14, 2014 at 8:38 AM, Yelu  wrote:
>>>
>>>> you can curl by using your username and password
>>>>
>>>> --os-username XX --os-password XX
>>>>
>>>> and check your conf here
>>>> are they correct
>>>> [image: Inline image 1]
>>>>
>>>>
>>>>
>>>>
>>>> On Sun, Apr 13, 2014 at 7:52 PM, Devendra Gupta wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> I have configured keystone to SSL and also update the endpoint in
>>>>> service catalog. Keystone operations like endpoint/tenant list working
>>>>> fine. I also update glance-api.conf and glance-registry.conf files
>>>>> with ssl enabled keystone details but still glance is unable to find
>>>>> images. It fails with following:
>>>>>
>>>>> [root@openstack-centos65 glance(keystone_admin)]# glance --insecure
>>>>> image-list
>>>>> Request returned failure status.
>>>>> Invalid OpenStack Identity credentials.
>>>>>
>>>>> Please see attached keystone.conf, glance-api.conf and
>>>>> glance-registry.conf and debug output of glance image-list and
>>>>> endpoint list.
>>&

Re: [Openstack] Glance Image list not working after Keystone SSL setup

2014-04-13 Thread Yaguang Tang 
I think you should add insecure=True to glance-api.conf and
glance-register.conf below keystone_authtoken section.


2014-04-14 12:45 GMT+08:00 Devendra Gupta :

> Ok Yelu, I am trying this, though glance image-list was working fine
> before configuring keystone to SSL. BTW please also see the SSL error I saw
> in glance api.log
>
> 2014-04-14 18:08:37.011 1989 INFO urllib3.connectionpool [-] Starting new
> HTTPS connection (1): openstack-centos65
> 2014-04-14 18:08:37.039 1989 WARNING keystoneclient.middleware.auth_token
> [-] Retrying on HTTP connection exception: [Errno 1] _ssl.c:492:
> error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify
> failed
> 2014-04-14 18:08:39.041 1989 INFO urllib3.connectionpool [-] Starting new
> HTTPS connection (1): openstack-centos65
> 2014-04-14 18:08:39.069 1989 ERROR keystoneclient.middleware.auth_token
> [-] HTTP connection exception: [Errno 1] _ssl.c:492: error:14090086:SSL
> routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
> 2014-04-14 18:08:39.069 1989 WARNING keystoneclient.middleware.auth_token
> [-] Authorization failed for token 123aa9518c869b95c2d75ab49f12c139
> 2014-04-14 18:08:39.070 1989 INFO keystoneclient.middleware.auth_token [-]
> Invalid user token - deferring reject downstream
>
> Regards,
> Devendra
>
> On Mon, Apr 14, 2014 at 8:38 AM, Yelu  wrote:
>
>> you can curl by using your username and password
>>
>> --os-username XX --os-password XX
>>
>> and check your conf here
>> are they correct
>> [image: Inline image 1]
>>
>>
>>
>>
>> On Sun, Apr 13, 2014 at 7:52 PM, Devendra Gupta wrote:
>>
>>> Hi,
>>>
>>> I have configured keystone to SSL and also update the endpoint in
>>> service catalog. Keystone operations like endpoint/tenant list working
>>> fine. I also update glance-api.conf and glance-registry.conf files
>>> with ssl enabled keystone details but still glance is unable to find
>>> images. It fails with following:
>>>
>>> [root@openstack-centos65 glance(keystone_admin)]# glance --insecure
>>> image-list
>>> Request returned failure status.
>>> Invalid OpenStack Identity credentials.
>>>
>>> Please see attached keystone.conf, glance-api.conf and
>>> glance-registry.conf and debug output of glance image-list and
>>> endpoint list.
>>>
>>> Regards,
>>> Devendra
>>>
>>> ___
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang

Canonical Ltd. | www.ubuntu.com | www.canonical.com
Mobile:  +86 152 1094 6968
gpg key: 0x187F664F
<>___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Challenges faced with Openstack keystone v3 API

2014-03-31 Thread Yaguang Tang 
Devendra,

yeah, Just as Joe said it's not supported  officially by OpenStack
community.

2014-04-01 10:38 GMT+08:00 Devendra Gupta :

> Thanks you Tang and Joe for your inputs. I'll give it a try in my Havana
> setup.
>
> Tang, I guess the solution you provided is not yet released in Havana. I
> mean to say if someone have latest released version setup of OpenStack
> Havana then by default he don't have Identity v3 compatibility for nova in
> his environment.
>
> Regards,
> Devendra
>
>
>
> On Tue, Apr 1, 2014 at 7:47 AM, Yaguang Tang  wrote:
>
>> so far, not all python-*client are ready for keystone v3, but if you want
>> to try do some testing the correct procedure is
>>
>> 1.  add or modify keystone identity service endpoints to v3  eg.
>> http://localhost:5000/v3
>> 2. change all openstack services auth_token middleware to use v3
>> authentication, e.g. add auth_version=3.0 in nova.conf under
>> [keystone_authtoken] section or in api-paste.ini file.
>> 3. you need the two python-novaclient patch
>> https://review.openstack.org/#/c/82149/ ,
>> https://review.openstack.org/#/c/81749/.
>> 4.  export OS_IDENTITY_API_VERSION=3
>> export OS_AUTH_URL=http://127.0.0.1:5000/v3
>>
>> then you should be able to use v3 token to do authentication,  run nova
>> --debug list and check the result.
>>
>>
>>
>>
>>
>>
>>
>>
>> 2014-04-01 0:47 GMT+08:00 Joe Gordon :
>>
>>
>>>
>>>
>>> On Mon, Mar 31, 2014 at 2:39 AM, Devendra Gupta wrote:
>>>
>>>> Hi,
>>>> We have been doing analysis around keystone v3 api for authenticating
>>>> with openstack components in Havana release but while doing so we are
>>>> facing some issues with the authentication using keytone v3 API .
>>>>
>>>> Below is the list of Components that we are using along with versions:-
>>>> *Compute : v2*
>>>> *Identity : v2.0 & v3*
>>>> *Network : v2*
>>>> *Image : v2*
>>>>
>>>>
>>>
>>>>
>>>> Following are the concerns that we have :-
>>>>
>>>> 1. After getting authentication token using API */v3/auth/tokens *and
>>>> supplying userid, password along with project scope , when we try to hit
>>>> Compute's API
>>>> *  v2/58d73fe0ec9c44e7a2127bf8abd60dc2/os-networks* we are getting
>>>> *Internal server error occured : code 500.*
>>>>
>>>
>>>
>>> Nova doesn't support keystone v3 yet.
>>>
>>>
>>>
>>>>
>>>>
>>>>  Moreover , even if we try to hit other components like Neutron we have
>>>> similar issues . However, when we hit the same API call with keystone v2.0
>>>> generated auth token we are able to get results as desired.
>>>>
>>>> Since keystone is by default enabled to use v3 and v2.0 , the tokens
>>>> generated by v3 should be able to authenticate for othe components like
>>>> nova, neutron , glance which it is not happening as of now.
>>>>
>>>> So is it a configuration issue or keystone v3 version is not yet
>>>> supported by other components.
>>>>
>>>> 2. Can there be a scenario where keystone will be setup with v3 only
>>>> instead of both v2.0 and v3.
>>>>
>>>> Please provide inputs on the above.
>>>>
>>>> Regards,
>>>> Devendra Gupta
>>>>
>>>> ___
>>>> Mailing list:
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>> Post to : openstack@lists.openstack.org
>>>> Unsubscribe :
>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>
>>>>
>>>
>>> ___
>>> Mailing list:
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>> Post to : openstack@lists.openstack.org
>>> Unsubscribe :
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>
>>>
>>
>>
>> --
>> Tang Yaguang
>>
>> Canonical Ltd. | www.ubuntu.com | www.canonical.com
>> Mobile:  +86 152 1094 6968
>> gpg key: 0x187F664F
>>
>>
>
>


-- 
Tang Yaguang

Canonical Ltd. | www.ubuntu.com | www.canonical.com
Mobile:  +86 152 1094 6968
gpg key: 0x187F664F
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Challenges faced with Openstack keystone v3 API

2014-03-31 Thread Yaguang Tang 
so far, not all python-*client are ready for keystone v3, but if you want
to try do some testing the correct procedure is

1.  add or modify keystone identity service endpoints to v3  eg.
http://localhost:5000/v3
2. change all openstack services auth_token middleware to use v3
authentication, e.g. add auth_version=3.0 in nova.conf under
[keystone_authtoken] section or in api-paste.ini file.
3. you need the two python-novaclient patch
https://review.openstack.org/#/c/82149/ ,
https://review.openstack.org/#/c/81749/.
4.  export OS_IDENTITY_API_VERSION=3
export OS_AUTH_URL=http://127.0.0.1:5000/v3

then you should be able to use v3 token to do authentication,  run nova
--debug list and check the result.








2014-04-01 0:47 GMT+08:00 Joe Gordon :

>
>
>
> On Mon, Mar 31, 2014 at 2:39 AM, Devendra Gupta wrote:
>
>> Hi,
>> We have been doing analysis around keystone v3 api for authenticating
>> with openstack components in Havana release but while doing so we are
>> facing some issues with the authentication using keytone v3 API .
>>
>> Below is the list of Components that we are using along with versions:-
>> *Compute : v2*
>> *Identity : v2.0 & v3*
>> *Network : v2*
>> *Image : v2*
>>
>>
>
>>
>> Following are the concerns that we have :-
>>
>> 1. After getting authentication token using API */v3/auth/tokens *and
>> supplying userid, password along with project scope , when we try to hit
>> Compute's API
>> *  v2/58d73fe0ec9c44e7a2127bf8abd60dc2/os-networks* we are getting
>> *Internal server error occured : code 500.*
>>
>
>
> Nova doesn't support keystone v3 yet.
>
>
>
>>
>>
>>  Moreover , even if we try to hit other components like Neutron we have
>> similar issues . However, when we hit the same API call with keystone v2.0
>> generated auth token we are able to get results as desired.
>>
>> Since keystone is by default enabled to use v3 and v2.0 , the tokens
>> generated by v3 should be able to authenticate for othe components like
>> nova, neutron , glance which it is not happening as of now.
>>
>> So is it a configuration issue or keystone v3 version is not yet
>> supported by other components.
>>
>> 2. Can there be a scenario where keystone will be setup with v3 only
>> instead of both v2.0 and v3.
>>
>> Please provide inputs on the above.
>>
>> Regards,
>> Devendra Gupta
>>
>> ___
>> Mailing list:
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>
>>
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang

Canonical Ltd. | www.ubuntu.com | www.canonical.com
Mobile:  +86 152 1094 6968
gpg key: 0x187F664F
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] [nova] No valid host found

2014-01-16 Thread Yaguang Tang 
from the exception we know an argument is not supported by python guestfs
,, I tested this in ubuntu 13.10, it works well,

ii  libguestfs0:amd64 1:1.22.4-1ubuntu1
amd64guest disk image management system -
shared library
ii  python-guestfs1:1.22.4-1ubuntu1
amd64guest disk image management system -
Python bindings

you can try to upgrade the related packages.


2014/1/14 Mark Vlcek (mavlcek) 

>  Following up, when I attempt to launch a medium flavor image, here's the
> output in the nova scheduler log file:
>
>  Error from last host: [u'Traceback (most recent call last):\n', u'  File
> "/opt/stack/nova/nova/compute/manager.py", line 1054, in _build_instance\n
>set_access_ip=set_access_ip)\n', u'  File
> "/opt/stack/nova/nova/compute/manager.py", line 357, in
> decorated_function\nreturn function(self, context, *args, **kwargs)\n',
> u'  File "/opt/stack/nova/nova/compute/manager.py", line 1463, in _spawn\n
>LOG.exception(_(\'Instance failed to spawn\'), instance=instance)\n', u'
>  File "/opt/stack/nova/nova/openstack/common/excutils.py", line 68, in
> __exit__\nsix.reraise(self.type_, self.value, self.tb)\n', u'  File
> "/opt/stack/nova/nova/compute/manager.py", line 1460, in _spawn\n
>  block_device_info)\n', u'  File
> "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2182, in spawn\n
>  admin_pass=admin_password)\n', u'  File
> "/opt/stack/nova/nova/virt/libvirt/driver.py", line 2485, in
> _create_image\nproject_id=instance[\'project_id\'])\n', u'  File
> "/opt/stack/nova/nova/virt/libvirt/imagebackend.py", line 187, in cache\n
>  *args, **kwargs)\n', u'  File
> "/opt/stack/nova/nova/virt/libvirt/imagebackend.py", line 337, in
> create_image\ncopy_qcow2_image(base, self.path, size)\n', u'  File
> "/opt/stack/nova/nova/openstack/common/lockutils.py", line 249, in inner\n
>return f(*args, **kwargs)\n', u'  File
> "/opt/stack/nova/nova/virt/libvirt/imagebackend.py", line 303, in
> copy_qcow2_image\ndisk.extend(target, size, use_cow=True)\n', u'  File
> "/opt/stack/nova/nova/virt/disk/api.py", line 149, in extend\nif not
> is_image_partitionless(image, use_cow):\n', u'  File
> "/opt/stack/nova/nova/virt/disk/api.py", line 189, in
> is_image_partitionless\nfs.setup()\n', u'  File
> "/opt/stack/nova/nova/virt/disk/vfs/guestfs.py", line 111, in setup\n
>  self.handle = tpool.Proxy(guestfs.GuestFS(close_on_exit=False))\n',
> u"TypeError: __init__() got an unexpected keyword argument
> 'close_on_exit'\n"]
>
>  And here is the contents of my nova.conf file:
>
>  [DEFAULT]
> flat_interface = eth1
> flat_network_bridge = br100
> vlan_interface = eth1
> public_interface = eth1
> network_manager = nova.network.manager.FlatDHCPManager
> firewall_driver = nova.virt.libvirt.firewall.IptablesFirewallDriver
> compute_driver = libvirt.LibvirtDriver
> use_usb_tablet = False
> libvirt_cpu_mode = none
> libvirt_type = qemu
> glance_api_servers = [my-ip-address]:9292
> rabbit_password = [my-rabbit-pw]
> rabbit_host = localhost
> rpc_backend = nova.openstack.common.rpc.impl_kombu
> ec2_dmz_host = [my-ip-address]
> vncserver_proxyclient_address = 127.0.0.1
> vncserver_listen = 127.0.0.1
> vnc_enabled = true
> xvpvncproxy_base_url = http://[my-ip-address]:6081/console
> novncproxy_base_url = http://[my-ip-address]:6080/vnc_auto.html
> notification_driver = nova.openstack.common.notifier.rpc_notifier
> notify_on_state_change = vm_and_task_state
> instance_usage_audit_period = hour
> instance_usage_audit = True
> logging_exception_prefix = %(color)s%(asctime)s.%(msecs)03d TRACE %(name)s
> %(instance)s
> logging_debug_format_suffix = from (pid=%(process)d) %(funcName)s
> %(pathname)s:%(lineno)d
> logging_default_format_string = %(asctime)s.%(msecs)03d
> %(color)s%(levelname)s %(name)s [-%(color)s]
> %(instance)s%(color)s%(message)s
> logging_context_format_string = %(asctime)s.%(msecs)03d
> %(color)s%(levelname)s %(name)s [%(request_id)s %(user_name)s
> %(project_name)s%(color)s] %(instance)s%(color)s%(message)s
> force_config_drive = always
> instances_path = /opt/stack/data/nova/instances
> lock_path = /opt/stack/data/nova
> state_path = /opt/stack/data/nova
> volume_api_class = nova.volume.cinder.API
> enabled_apis = ec2,osapi_compute,metadata
> bindir = /usr/bin
> instance_name_template = instance-%08x
> fatal_deprecations = True
> sql_connection = mysql://root:[mysql-pw]@127.0.0.1/nova?charset=utf8
> metadata_workers = 4
> ec2_workers = 4
> osapi_compute_workers = 4
> my_ip = [my-ip-address]
> osapi_compute_extension =
> nova.api.openstack.compute.contrib.standard_extensions
> s3_port = 
> s3_host = [my-ip-address]
> default_floating_pool = public
> fixed_range =
> force_dhcp_release = True
> dhcpbridge_flagfile = /etc/nova/nova.conf
> scheduler_driver = nova.scheduler.filter_scheduler.FilterScheduler
> rootwrap_config = /etc/nova/rootwrap.conf
> api_paste_config = /etc/nova/

Re: [Openstack] Unable to see console using VNC on ESX hypervisor

2013-11-21 Thread Yaguang Tang 
2013年11月21日 下午10:02于 "Yaguang Tang" 写道：
>
> Grizzly openstack doesn't support vnc console with ESX driver.

sorry， i mean  vnc console log is not supported.
>
> 2013年11月21日 下午9:43于 "Rajshree Thorat" 写道：
>
>> Hi All,
>>
>> I have configured OpenStack Grizzly to control ESX hypervisor. I can
successfully launch instances but unable to see its console using VNC.
>>
>> Following is my configuration.
>>
>> ***Compute node :
>>
>> nova.conf for vnc:
>>
>> vnc_enabled = true
>> novncproxy_base_url=http://public_ip_of_controller:6080/vnc_auto.html
>> novncproxy_port=6080
>> vncserver_proxyclient_address=management_ip_of_compute
>> vncserver_listen=0.0.0.0
>>
>> ***Controller node:
>>
>> nova.conf for vnc:
>>
>> novncproxy_base_url=http://public_ip_of_controller:6080/vnc_auto.html
>> novncproxy_port=6080
>> vncserver_proxyclient_address=management_ip_of_controller
>> vncserver_listen=0.0.0.0
>>
>> root@openstk2:~# tail /var/log/nova/nova-consoleauth.log
>> 2013-11-21 18:40:35.228 7570 AUDIT nova.service [-] Starting consoleauth
node (version 2013.1.3)
>> 2013-11-21 18:40:35.395 INFO nova.openstack.common.rpc.common
[req-179d456d-f306-426f-b65e-242362758f73 None None] Connected to AMQP
server on controller_ip:5672
>> 2013-11-21 18:42:34.012 AUDIT nova.consoleauth.manager
[req-ebc33f34-f57b-492b-8429-39eb3240e5d7 a8f0e9af6e6b4d08b1729acae0510d54
db63e4a448fc426086562638726f9081] Received Token:
1bcb7408-5c59-466d-a84d-528481af3c37, {'instance_uuid':
u'969e49b0-af3f-45bd-8618-1320ba337962', 'internal_access_path': None,
'last_activity_at': 1385039554.012067, 'console_type': u'novnc', 'host':
u'ESX_host_IP', 'token': u'1bcb7408-5c59-466d-a84d-528481af3c37', 'port':
6031})
>> 2013-11-21 18:42:34.015 INFO nova.openstack.common.rpc.common
[req-ebc33f34-f57b-492b-8429-39eb3240e5d7 a8f0e9af6e6b4d08b1729acae0510d54
db63e4a448fc426086562638726f9081] Connected to AMQP server on
controller_ip:5672
>> 2013-11-21 18:42:34.283 AUDIT nova.consoleauth.manager
[req-518ed47e-5d68-491d-8c57-16952744a2d8 None None] Checking Token:
1bcb7408-5c59-466d-a84d-528481af3c37, True)
>> 2013-11-21 18:42:35.710 AUDIT nova.consoleauth.manager
[req-2d65d8ac-c003-4f4d-9014-9e8995794ad6 None None] Checking Token:
1bcb7408-5c59-466d-a84d-528481af3c37, True)
>>
>> With same configuration I can connect to vm's console on KVM setup. Is
there any other setting to access console for ESX hypervisor?
>>
>> Any help would be highly appreciated.
>>
>> Thanks in advance,
>>
>> Regards,
>> Rajshree
>>
>>
>>
>>
>> ___
>> Mailing list:
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>> Post to : openstack@lists.openstack.org
>> Unsubscribe :
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Unable to see console using VNC on ESX hypervisor

2013-11-21 Thread Yaguang Tang 
Grizzly openstack doesn't support vnc console with ESX driver.
2013年11月21日 下午9:43于 "Rajshree Thorat" 写道：

> Hi All,
>
> I have configured OpenStack Grizzly to control ESX hypervisor. I can
> successfully launch instances but unable to see its console using VNC.
>
> Following is my configuration.
>
> ***Compute node :
>
> nova.conf for vnc:
>
> vnc_enabled = true
> novncproxy_base_url=http://public_ip_of_controller:6080/vnc_auto.html
> novncproxy_port=6080
> vncserver_proxyclient_address=management_ip_of_compute
> vncserver_listen=0.0.0.0
>
> ***Controller node:
>
> nova.conf for vnc:
>
> novncproxy_base_url=http://public_ip_of_controller:6080/vnc_auto.html
> novncproxy_port=6080
> vncserver_proxyclient_address=management_ip_of_controller
> vncserver_listen=0.0.0.0
>
> root@openstk2:~# tail /var/log/nova/nova-consoleauth.log
> 2013-11-21 18:40:35.228 7570 AUDIT nova.service [-] Starting consoleauth
> node (version 2013.1.3)
> 2013-11-21 18:40:35.395 INFO nova.openstack.common.rpc.common
> [req-179d456d-f306-426f-b65e-242362758f73 None None] Connected to AMQP
> server on controller_ip:5672
> 2013-11-21 18:42:34.012 AUDIT nova.consoleauth.manager
> [req-ebc33f34-f57b-492b-8429-39eb3240e5d7 a8f0e9af6e6b4d08b1729acae0510d54
> db63e4a448fc426086562638726f9081] Received Token: 
> 1bcb7408-5c59-466d-a84d-528481af3c37,
> {'instance_uuid': u'969e49b0-af3f-45bd-8618-1320ba337962',
> 'internal_access_path': None, 'last_activity_at': 1385039554.012067,
> 'console_type': u'novnc', 'host': u'ESX_host_IP', 'token':
> u'1bcb7408-5c59-466d-a84d-528481af3c37', 'port': 6031})
> 2013-11-21 18:42:34.015 INFO nova.openstack.common.rpc.common
> [req-ebc33f34-f57b-492b-8429-39eb3240e5d7 a8f0e9af6e6b4d08b1729acae0510d54
> db63e4a448fc426086562638726f9081] Connected to AMQP server on
> controller_ip:5672
> 2013-11-21 18:42:34.283 AUDIT nova.consoleauth.manager
> [req-518ed47e-5d68-491d-8c57-16952744a2d8 None None] Checking Token:
> 1bcb7408-5c59-466d-a84d-528481af3c37, True)
> 2013-11-21 18:42:35.710 AUDIT nova.consoleauth.manager
> [req-2d65d8ac-c003-4f4d-9014-9e8995794ad6 None None] Checking Token:
> 1bcb7408-5c59-466d-a84d-528481af3c37, True)
>
> With same configuration I can connect to vm's console on KVM setup. Is
> there any other setting to access console for ESX hypervisor?
>
> Any help would be highly appreciated.
>
> Thanks in advance,
>
> Regards,
> Rajshree
>
>
>
>
> ___
> Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/
> openstack
>
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack

Re: [Openstack] Troubleshooting when launching instances

2013-11-12 Thread Yaguang Tang 
could you provide  the nova-compute.log  info to help debug.


2013/11/12 Stephane EVEILLARD 

> Hi
>
> I just finished installing my controller (Havana) and also installed a node
> Everything was ok
> but when I try to start an instance, It goes from spawning to error
> and I didn't get error messages
> I tried with Iso and qcow2 and get the same result
>
> Any help is welcome
>
> Regards
>
> --
> Stéphane EVEILLARD
> Responsable Système et Développement IBS NETWORK
> Coordinateur Version Française Openstack
>
> ___
> Mailing list:
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
> Post to : openstack@lists.openstack.org
> Unsubscribe :
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>
>


-- 
Tang Yaguang

Canonical Ltd. | www.ubuntu.com | www.canonical.com
Mobile:  +86 152 1094 6968
gpg key: 0x187F664F
___
Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
Post to : openstack@lists.openstack.org
Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack