from:"Erlon Cruz"

Re: [Openstack] OpenStack 2014.1 ("Icehouse") is released !

2014-04-17 Thread Erlon Cruz

Great! Good news!


On Thu, Apr 17, 2014 at 10:40 AM, Heiko Krämer wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Oh really nice.
>
> Good job guys and girls!!!
>
> On 17.04.2014 15:01, Thierry Carrez wrote:
> > Hi everyone,
> >
> > I'm proud to announce the final release of OpenStack 2014.1,
> > code-named "Icehouse". This marks the completion of a 6-month
> > journey which started at the Icehouse Design Summit in Hong-Kong.
> > During this cycle we added a new integrated component (Trove),
> > completed more than 350 feature blueprints and fixed almost 3000
> > reported bugs in integrated projects alone !
> >
> > You can find source tarballs for each integrated project, together
> > with complete lists of features and bugfixes, at the following
> > links:
> >
> > Compute (Nova):
> > https://launchpad.net/nova/icehouse/2014.1 Object Storage (Swift):
> > https://launchpad.net/swift/icehouse/1.13.1 Image Service (Glance):
> > https://launchpad.net/glance/icehouse/2014.1 Networking (Neutron):
> > https://launchpad.net/neutron/icehouse/2014.1 Block Storage
> > (Cinder):   https://launchpad.net/cinder/icehouse/2014.1 Identity
> > (Keystone):  https://launchpad.net/keystone/icehouse/2014.1
> > Dashboard (Horizon):
> > https://launchpad.net/horizon/icehouse/2014.1 Telemetry
> > (Ceilometer):   https://launchpad.net/ceilometer/icehouse/2014.1
> > Orchestration (Heat):
> > https://launchpad.net/heat/icehouse/2014.1 Database Service
> > (Trove): https://launchpad.net/trove/icehouse/2014.1
> >
> > The Icehouse Release Notes contain an overview of the key features,
> > as well as upgrade notes and current lists of known issues. You can
> > access them at:
> >
> > https://wiki.openstack.org/wiki/ReleaseNotes/Icehouse
> >
> > Thanks to the hundreds of people who contributed to this
> > development cycle and helped in making this release great !
> >
>
> - --
> Anynines.com
>
> B.Sc. Informatik
> CIO
> Heiko Krämer
>
>
> Twitter: @anynines
>
> - - 
> Geschäftsführer: Alexander Faißt, Dipl.-Inf.(FH) Julian Fischer
> Handelsregister: AG Saarbrücken HRB 17413, Ust-IdNr.: DE262633168
> Sitz: Saarbrücken
> Avarteq GmbH
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.4.14 (GNU/Linux)
> Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJTT9m5AAoJELxFogM4ixOFPRAH/iaiV4SJLth+GfQw7KivlMTi
> m6ZGUGIDLoHBFvAUjyXReYrfvvBCRm9m8udxOJQLV+gCEEE3RVJpCSl+mtXs31IV
> elYckO0MPQ/zXu1jhOr6hDvG3VV0XTmkixHqsM7M7GP7dijnFrrrcl183/PqUuzo
> j55Ax75OIxn5VL8L9byy6vDzIeP5846ttcRrkucs9mNYy/IJoeDvz7/8XP4Ug5vA
> IwQ8c2uwMy7YPwP4ZQPCv32HxpFLsZa/9+sPqoIOdDS6/BN443fOyXmV/uBlwuTv
> mxcxgWmt5F7ropnlktkuvvl4Q/u0F7WQwrSeBo52mX2yLqwOWfNMQ/4IChnK0AQ=
> =tqHC
> -END PGP SIGNATURE-
>
> ___
> 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] [openstack-dev] how and which tempest tests to run

2014-08-01 Thread Erlon Cruz

Hi Nikesh,

There's a script in devstack, 'driver_certs/cinder_driver_cert.sh' that is
used to test third party drivers. It will run all the necessary tests to
get your driver tested. After run, the script says if your driver passed or
failed. I see that you are using TEMPEST_VOLUME_DRIVER,  TEMPEST_VOLUME_VENDOR
and TEMPEST_STORAGE_PROTOCOL. I usually set those options on
 /opt/stack/tempest/etc/tempest.conf. Not sure if they are the same, but
worth to change if your driver is not passing.

Erlon


On Fri, Aug 1, 2014 at 5:32 AM, Nikesh Kumar Mahalka <
nikeshmaha...@vedams.com> wrote:

> I deployed a single node devstack on Ubuntu 14.04.
> This devstack belongs to Juno.
> I have written a cinder-volume driver for my client backend.
> I want to contribute this driver in Juno release.
> As i analyzed the contribution process,it is telling to run tempest tests
> for Continuous Integration.
>
> Could any one tell me how and which tempest tests to run on this devstack
> deployment for cinder volume driver?
> Also tempest has many test cases.Do i have to pass all tests for
> contribution of my driver?
>
> Also am i missing any thing thing in below local.conf?
>
> *Below are steps for my devstack deployment:*
>
> 1) git clone https://github.com/openstack-dev/devstack.git
> 2)cd devstack
> 3)vi local.conf
>
> [[local|localrc]]
>
> ADMIN_PASSWORD=some_password
> DATABASE_PASSWORD=$ADMIN_PASSWORD
> RABBIT_PASSWORD=$ADMIN_PASSWORD
> SERVICE_PASSWORD=$ADMIN_PASSWORD
> SERVICE_TOKEN=ADMIN
> FLAT_INTERFACE=eth0
> FIXED_RANGE=192.168.2.80/29
> #FLOATING_RANGE=192.168.20.0/25
> HOST_IP=192.168.2.64
> LOGFILE=$DEST/logs/stack.sh.log
> SCREEN_LOGDIR=$DEST/logs/screen
> SYSLOG=True
> SYSLOG_HOST=$HOST_IP
> SYSLOG_PORT=516
> RECLONE=yes
> CINDER_ENABLED_BACKENDS=client:client_driver
> TEMPEST_VOLUME_DRIVER=client_iscsi
> TEMPEST_VOLUME_VENDOR="CLIENT"
> TEMPEST_STORAGE_PROTOCOL=iSCSI
> VOLUME_BACKING_FILE_SIZE=20G
>
> [[post-config|$CINDER_CONF]]
>
> [client_driver]
> volume_driver=cinder.volume.drivers.san.client.iscsi.
> client_iscsi.ClientISCSIDriver
> san_ip = 192.168.2.192
> san_login = some_name
> san_password =some_password
> client_iscsi_ips = 192.168.2.193
>
> 4)./stack.sh
>
>
> ___
> OpenStack-dev mailing list
> openstack-...@lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
___
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] [Cinder] deploying multiple backend

2014-09-10 Thread Erlon Cruz

Hi Jyoti,

No. Each cinder.conf can be different. It can be a complete separate
configuration(LVM, FC, iSCSI). The scheduler and the volume service doesn't
 need to share the same config file either.

On Fri, Sep 5, 2014 at 2:54 PM, Jyoti Ranjan  wrote:

> Hi,
>
> I have three nodes say N1, N2 and N3 where I want to deploy LVM and want
> to consume for volume provisioning using common backend name say Group-LVM.
> Can you help me for following questions:
>
>
> Do I need to have exactly same cinder.conf for all three instances of
> cinder-volume? I think no  as it will result in running three cinder-volume
> backend instances on each node. In total, it will be 9 instances of
> cinder-volume publishing capabilities to cinder-scheduler.
>
> Regards,
> Jyoti Ranjan
>
> ___
> 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] Cinder | Volume creation stuck in the "creating" status

2014-10-10 Thread Erlon Cruz

What does cinder-scheduler and cinder-api logs say?

On Fri, Oct 10, 2014 at 10:10 AM, Mridhul Pax  wrote:

> Hi Stackers,
>
> Im seeing a strange behaviour in the cinder volume creation where the
> volume creation is stuck in the creating status.
>
> # cinder list
>
> +--+--+--+--+-+--+-+
> |  ID  |  Status  | Display Name | Size |
> Volume Type | Bootable | Attached to |
>
> +--+--+--+--+-+--+-+
> | 49538a8c-c1bc-4f0b-a6c8-d43dfcdb0518 |* creating |* dsa  |  1
> | None|  false   | |
>
> +--+--+--+--+-+--+-+
>
> Here is my cinder.conf
>
> [DEFAULT]
>
> #
>
> rootwrap_config = /etc/cinder/rootwrap.conf
> api_paste_confg = /etc/cinder/api-paste.ini
> iscsi_helper = tgtadm
> volume_name_template = volume-%s
> volume_group = cinder-volumes
> verbose = True
> auth_strategy = keystone
> state_path = /var/lib/cinder
> lock_path = /var/lock/cinder
> volumes_dir = /var/lib/cinder/volumes
>
> glance_host = controller
>
>  RABBBIT
>
> #rpc_backend = cinder.openstack.common.rpc.impl_kombu
> rpc_backend = rabbit
> rabbit_host = controller
> rabbit_port = 5672
> rabbit_userid = guest
> rabbit_password = **
>
> [database]
> connection = mysql://cinder:@controller/cinder
>
> [keystone_authtoken]
> auth_uri = http://controller:5000
> auth_host = controller
> auth_port = 35357
> auth_protocol = http
> admin_tenant_name = service
> admin_user = cinder
> admin_password = **
>
> I checked the logs and nothing getting logged in the cinder server as
> well//./
>
>
> Please share you inputs
>
> regards
> Mridhul
>
>
> ___
> 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] Cinder type-create error during Devstack installation

2015-04-24 Thread Erlon Cruz

I have had many problems with ./unstack.sh and often have seen people with
the same problems. For me it is not reliable. So what I always recommend
is, start fresh, and if possible save the live state of the VM after
devstack finishes so you do have to start all over.

On Wed, Apr 22, 2015 at 12:59 PM, Silvia Fichera 
wrote:

> I have already done those passages... unstack.sh, clean.sh, delete
> /opt/stack and stack again. It does not work
>
> Il giorno mer 22 apr 2015 alle ore 17:40 Abhishek Shrivastava <
> abhis...@cloudbyte.com> ha scritto:
>
>> Are you recloning the projects also?
>>
>> If not then do the clean.sh and then delete the /opt/stack/ folder and do
>> the stack.sh again. The error may have caused due to the old repositories
>> of projects in /opt/stack/
>>
>> On Wed, Apr 22, 2015 at 6:36 PM, Silvia Fichera 
>> wrote:
>>
>>> Hi Abhishek,
>>> the result of the command git status inside the devstack forlder is this:
>>>
>>> On branch master
>>> Your branch is up-to-date with 'origin/master'.
>>>
>>> Untracked files:
>>>   (use "git add ..." to include in what will be committed)
>>>
>>> tmp-venv-HMry/
>>> tmp-venv-ReEW/
>>>
>>> nothing added to commit but untracked files present (use "git add" to
>>> track)
>>>
>>>
>>> Il giorno mer 22 apr 2015 alle ore 13:54 Abhishek Shrivastava <
>>> abhis...@cloudbyte.com> ha scritto:
>>>
 Hi Silvia,

 Can you please do a *git status* and then tell me which devstack
 version are you using?

 On Wed, Apr 22, 2015 at 5:04 PM, Silvia Fichera 
 wrote:

> Hi all, I'm re-installing OpenStack using Devstack and I'm building a
> multinode environment. Starting from the installation of the Controller
> node, it fails and says:
>
> > cinder type-create lvmdriver-1> 2015-04-21 15:02:49.370 | ERROR: Unable 
> > to establish connection to> 
> > http://10.30.3.117:8776/v1/e06dceea27b6469bb0cf5c2f075da581/types> 
> > 2015-04-21 15:02:50.067 | ++ err_trap> 2015-04-21 15:02:50.069 | ++ 
> > local r=1> 2015-04-21 15:02:50.166 | Error on> exit
>
> Two days ago I have already installed it, but yesterday morning I had
> some problem and decided to *unstack* and *stack* again everything. I
> have *unstacked* in all compute hosts and also in the controller,
> than I've done *./clean.sh* and removed the folder /opt/stack. But
> now I can't install it anymore. Could someone help me please?
>
> Moreover when I unstack I have:
>
> Volume group "stack-volumes-lvmdriver-1" not found Skipping volume
> group stack-volumes-lvmdriver-1
>
> And when I did ./clean.sh I have this error:
>
> /home/stack/devstack/lib/cinder_backends/lvm: line 41:
> clean_lvm_volume_group: command not found
>
> Thanks for your help.
>
> ___
> 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
>
>


 --


 *Thanks & Regards,*
 *Abhishek*
 *Cloudbyte Inc. *

>>>
>>
>>
>> --
>>
>>
>> *Thanks & Regards,*
>> *Abhishek*
>> *Cloudbyte Inc. *
>>
>
> ___
> 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] Accelerating the Enterprise Adoption of OpenStack

2015-07-27 Thread Erlon Cruz

That are great news!! I'm really glad to know that!
Congratulations, Rackspace and Intel for the effort!

On Thu, Jul 23, 2015 at 2:01 PM, Egle Sigler 
wrote:

>  Hello OpenStack Community,
>
>
>
> I am very excited to let you know that today Rackspace and Intel announced
> our plans to form the “OpenStack Innovation Center,” which is an exciting
> community-oriented initiative focused on accelerating the enterprise
> features and adoption of OpenStack.  This initiative includes:
>
>
>
> ·  *Largest OpenStack Developer Cloud *– We are building and making
> available to the community two 1,000 node clusters to support advanced,
> large-scale and testing of OpenStack.  The clusters should be available to
> the community within six months and you can sign up here
>  to receive updates on this effort.
>
> ·  *OpenStack Developer Training* – We are creating a new training
> curriculum designed to onboard and significantly increase the number of
> developers working upstream in the community.
>
> ·  *Joint OpenStack Engineering* – Rackspace and Intel developers
> will work together in collaboration with the Enterprise Work Group and
> community to eliminate bugs and develop new enterprise features.  Both
> companies will recruit new developers to help further OpenStack development.
>
> ·  *OpenStack Innovation Center *– The center will be comprised of
> Rackspace and Intel developers who will work upstream, using existing
> community tools and processes to improve the scalability, manageability and
> usability of OpenStack.
>
>
>
> To find out more, please check out the following resources:
>
>
>
> Rackspace press release
> 
>
> Rackspace blog
> 
>
> Intel release
> 
>
> Intel blog
> 
>
>
>
> We look forward to working with you to continue advancing the leading open
> source cloud platform and welcome your feedback!
>
>
>
> Best regards,
>
>
>
> Egle Sigler
>
> Rackspace Principal Architect
>
> OpenStack Foundation Board Member
>
> ___
> 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] Cinder, custom filters and weighers.

2015-08-25 Thread Erlon Cruz

Hi Thomas,

Is you class inheriting from 'filters.BaseHostFilter'? Also, there's no
such option 'scheduler_available_filters' in openstack/icehouse.
A good way to have an insight of your problem is to put logs into
'cinder/scheduler/host_manager.py -> _choose_host_filters'.

Erlon

On Tue, Aug 25, 2015 at 9:02 AM, Shinobu  wrote:

> Yes, it's possible using inspectors.
>
> Shinobu
>
> On Tue, Aug 25, 2015 at 8:32 PM, Thomas Zilio  wrote:
>
>> Hello,
>>
>> I'm trying to test some custom cinder filters and weighers but I can't
>> manage to make it work.
>> I did the same for Nova and everything is working but the Cinder
>> scheduler can't seem to find my custom classes.
>>
>> My tests are made on a Icehouse installation.
>>
>> The error message appearing in the log is the following one:
>> > SchedulerHostFilterNotFound: Scheduler Host Filter CustomFilter could
>> not be found.
>>
>> The filter file is in the directory :
>> /usr/lib/python2.6/site-packages/cinder/scheduler/filters
>> And I added these lines to the cinder.conf file (not sure if the first
>> one is required).
>> > scheduler_available_filters=custom_filter.CustomFilter
>> >
>> scheduler_default_filters=AvailabilityZoneFilter,CapacityFilter,CapabilitiesFilter,CustomFilter
>>
>> My filter file name is custom_filter.py and the class is CustomFilter.
>>
>> I don't think it's related to what my filter does since it's not even
>> found by the scheduler.
>> I'm encountering the same issues with the weighers (and everything is
>> working just fine on the Nova scheduler side).
>>
>> If anyone has any idea how I could make this work I would be really
>> grateful !
>>
>> Thanks and regards,
>> Thomas
>> ___
>> 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
>>
>
>
>
> --
> Email:
>  shin...@linux.com
>  ski...@redhat.com
>
>  Life w/ Linux 
>
> ___
> 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] Cinder

2015-09-29 Thread Erlon Cruz

Have you checked nova-cpu locgs? Usually attach errors are logged there.

On Mon, Sep 28, 2015 at 6:34 AM, venkatesh kotipalli <
openstackvenkat...@gmail.com> wrote:

> Hi lvan,
>
> Thank you for your reply.
>
> I search the logs there is no errors.
>
> Thank you,
> Venkatesh.k
>
> On Mon, Sep 28, 2015 at 2:54 PM, Ivan Kolodyazhny  wrote:
>
>> Hi,
>>
>> Do you have any errors in Cinder and/or Nova logs?
>>
>> Regards,
>> Ivan Kolodyazhny
>>
>> On Mon, Sep 28, 2015 at 11:41 AM, venkatesh kotipalli <
>> openstackvenkat...@gmail.com> wrote:
>>
>>> Hi All,
>>>
>>> I have created a volume successfully. When am try to attach the volume
>>> to the instance it take long time but it won't attached to instance.
>>>
>>> Any one please help me guys.
>>>
>>> Thank you,
>>> Venkatesh.k
>>>
>>> ___
>>> 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

Re: [Openstack] Cinder Multiple Backends - Filter On Tenant

2016-03-19 Thread Erlon Cruz

Hi Brent,

Unfortunately that is not possible. The feature mentioned by Vahric,
driver_filter, is a 'driver' custom filter capability. I.e., the vendor
driver must implement that in order to be possible to use (surely, nothing
holds you from implementing in the driver if your vendor does not supports
it). You are trying to filter based in the volume size, the exiting
filters, filter based in the host's available size not the volume.

About the tenant filtering, the closest solution I can think of is is you
create a volume type associated with the backend you want to cast volumes o
the tenant, and then remove the permissions of all other available
volume-types so, the tenant only sees that volume type.

Can you give the reason why you need to filter like that? This could be a
good addition to future Cinder features.

Erlon

On Thu, Feb 25, 2016 at 7:57 PM, Brent Troge 
wrote:

> yeah, i have read through those, plus i did some reading through the
> actual code of all kilo/stable cinder filters
>
> i any case i think i have a good path forward, just need to start testing
> to understand this a bit more.
>
> thanks for taking the time to assist.
>
>
> On Thu, Feb 25, 2016 at 9:13 AM, Vahric Muhtaryan 
> wrote:
>
>> I found this
>>
>>
>> http://docs.openstack.org/admin-guide-cloud/blockstorage-driver-filter-weighing.html
>>
>> And this
>>
>>
>> https://blueprints.launchpad.net/cinder/+spec/filtering-weighing-with-driver-supplied-functions
>>
>> From: Brent Troge 
>> Date: Thursday 25 February 2016 at 16:17
>> To: "openstack@lists.openstack.org" 
>> Subject: [Openstack] Cinder Multiple Backends - Filter On Tenant
>>
>> I need the cinder filter to support directing volumes to a specific
>> backend based on tenant id and volume size.
>>
>> Something like:
>>
>> # tenant specific backend
>> [backend-1]
>> filter = (volume_size > 100G) && (tenant_id == abc123)
>>
>> # all others
>> [backend-2]
>> filter = (volume_size < 100G)
>>
>>
>>
>> Is this possible with the current set of kilo stable cinder filters ?
>>
>> Thanks in advance.
>>
>>
>> ___ 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

Re: [Openstack] Fw: Re: Cinder Multiple Backends - Filter On Tenant

2016-03-21 Thread Erlon Cruz

As I mentioned, setting the proper permissions would allow to cast all
tenant's volume to a backend, but wouldn't allow to filter based on the
volume size. There's no filters that does that today. An idea that could be
used is what is used in the json_filter. It allows the user to set a rules
like:

cinder create  --os-volume-api-version --hint
query='[">=","$free_capacity_gb",500]' vol1

But this does not allow to filter based in the volume's properties.
Furthermore, the admin can not make that mandatory for the tenant (not that
I know of). If the tenant does not set the 'hint', the request will follow
the default rules. If Cinder supported a filter definition in the backend
configuration, like Brent posted, that would be very useful (I have already
being asked about a similar request).



On Sun, Mar 20, 2016 at 2:00 PM, John Griffith 
wrote:

>
>
> On March 19, 2016 at 19:13:33, Erlon Cruz (sombra...@gmail.com) wrote:
>>
>> Hi Brent,
>>
>> Unfortunately that is not possible. The feature mentioned by Vahric,
>> driver_filter, is a 'driver' custom filter capability. I.e., the vendor
>> driver must implement that in order to be possible to use (surely, nothing
>> holds you from implementing in the driver if your vendor does not supports
>> it). You are trying to filter based in the volume size, the exiting
>> filters, filter based in the host's available size not the volume.
>>
>> About the tenant filtering, the closest solution I can think of is is you
>> create a volume type associated with the backend you want to cast volumes o
>> the tenant, and then remove the permissions of all other available
>> volume-types so, the tenant only sees that volume type.
>>
>> Can you give the reason why you need to filter like that? This could be a
>> good addition to future Cinder features.
>>
>> Erlon
>>
>> On Thu, Feb 25, 2016 at 7:57 PM, Brent Troge 
>> wrote:
>>
>>> yeah, i have read through those, plus i did some reading through the
>>> actual code of all kilo/stable cinder filters
>>>
>>> i any case i think i have a good path forward, just need to start
>>> testing to understand this a bit more.
>>>
>>> thanks for taking the time to assist.
>>>
>>>
>>> On Thu, Feb 25, 2016 at 9:13 AM, Vahric Muhtaryan 
>>> wrote:
>>>
>>>> I found this
>>>>
>>>>
>>>> http://docs.openstack.org/admin-guide-cloud/blockstorage-driver-filter-weighing.html
>>>>
>>>> And this
>>>>
>>>>
>>>> https://blueprints.launchpad.net/cinder/+spec/filtering-weighing-with-driver-supplied-functions
>>>>
>>>> From: Brent Troge 
>>>> Date: Thursday 25 February 2016 at 16:17
>>>> To: "openstack@lists.openstack.org" 
>>>> Subject: [Openstack] Cinder Multiple Backends - Filter On Tenant
>>>>
>>>> I need the cinder filter to support directing volumes to a specific
>>>> backend based on tenant id and volume size.
>>>>
>>>> Something like:
>>>>
>>>> # tenant specific backend
>>>> [backend-1]
>>>> filter = (volume_size > 100G) && (tenant_id == abc123)
>>>>
>>>> # all others
>>>> [backend-2]
>>>> filter = (volume_size < 100G)
>>>>
>>>>
>>>>
>>>> Is this possible with the current set of kilo stable cinder filters ?
>>>>
>>>> Thanks in advance.
>>>>
>>>>
>>>> ___ 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
>>
>> Hi Erlon,
>
> Cinder has the ability to set access rights on Volume Types.  I haven't
> looked at it in a while, but what you could do is set the type up based on
> the backend, and then apply access to the tenant you want there.
>
> One thing I guess we'd need to consider is different default types
> per/tenant which seems like it would be a useful feature if there's not
> already a way to make it work.
>
> John
>
>
___
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] Cinder Instance Locality Filter Error

2016-05-24 Thread Erlon Cruz

 Cinder is trying to reach back to nova but is failing. I think it might be
because it's trying to use Nova v1. "in _v1_auth". What do you have in
cinder.conf?

On Tue, May 24, 2016 at 6:14 PM, Brent Troge 
wrote:

> Hello all..
>
> I am trying to understand how to setup the cinder instance locality filter. I 
> think
>
> I have everything configured properly, however my cinder create commands fail
>
> when I pass a scheduler hint.
>
> When I omit the scheduler hint, the cinder volume is created as expected.
>
> Below are some datapoints I think the community may find useful in helping
>
> me with this issue.
>
> Thanks!
>
>
> Operating System - Ubuntu Trusty-64
> Openstack Release - Liberty
>
>
> COMMAND:
>
> cinder create --hint local_to_instance= 2
>
>
> CONFIGURATIONS
>
> nova.conf - api server
>
> [DEFAULT]
> #applicable directives
>
> nova_endpoint_template = http://controller:8774/v2/%(project_id)s
> nova_endpoint_admin_template =  http://controller:8774/v2/%(project_id)s
> scheduler_available_filters=cinder.scheduler.filters.BaseHostFilter
> scheduler_default_filters=InstanceLocalityFilter
> os_privileged_user_auth_url = http://controller:35357
> os_privileged_user_name = nova
> os_privileged_user_password = mypassword
> os_privileged_user_tenant = service
>
>
> PACKAGES INSTALLED
>
> nova-api/cinder-api server
>
> ii  cinder-api   2:7.0.2-0ubuntu1~cloud0   
> all  Cinder storage service - API server
> ii  cinder-common2:7.0.2-0ubuntu1~cloud0   
> all  Cinder storage service - common files
> ii  cinder-scheduler 2:7.0.2-0ubuntu1~cloud0   
> all  Cinder storage service - Scheduler server
> ii  nova-api 2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute - API frontend
> ii  nova-cert2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute - certificate management
> ii  nova-common  2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute - common files
> ii  nova-conductor   2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute - conductor service
> ii  nova-consoleauth 2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute - Console Authenticator
> ii  nova-novncproxy  2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute - NoVNC proxy
> ii  nova-scheduler   2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute - virtual machine scheduler
> ii  python-cinder2:7.0.2-0ubuntu1~cloud0   
> all  Cinder Python libraries
> ii  python-cinderclient  1:1.4.0-2~cloud0  
> all  Python bindings to the OpenStack Volume API - Python 2.x
> ii  python-nova  2:12.0.3-0ubuntu1~cloud0  
> all  OpenStack Compute Python libraries
> ii  python-novaclient2:2.30.1-1~cloud0 
> all  client library for OpenStack Compute API
>
>
>
> nova-compute/cinder-volume server
>
> ii  cinder-common   2:7.0.2-0ubuntu1~cloud0   
>  all  Cinder storage service - common files
> ii  cinder-volume   2:7.0.2-0ubuntu1~cloud0   
>  all  Cinder storage service - Volume server
> ii  nova-common 2:12.0.3-0ubuntu1~cloud0  
>  all  OpenStack Compute - common files
> ii  nova-compute2:12.0.3-0ubuntu1~cloud0  
>  all  OpenStack Compute - compute node base
> ii  nova-compute-kvm2:12.0.3-0ubuntu1~cloud0  
>  all  OpenStack Compute - compute node (KVM)
> ii  nova-compute-libvirt2:12.0.3-0ubuntu1~cloud0  
>  all  OpenStack Compute - compute node libvirt support
> ii  python-cinder   2:7.0.2-0ubuntu1~cloud0   
>  all  Cinder Python libraries
> ii  python-cinderclient 1:1.4.0-2~cloud0  
>  all  Python bindings to the OpenStack Volume API - Python 2.x
> ii  python-nova 2:12.0.3-0ubuntu1~cloud0  
>  all  OpenStack Compute Python libraries
> ii  python-novaclient   2:2.30.1-1~cloud0 
>  all  client library for OpenStack Compute API
>
>
>
> CINDER SCHEDULER LOGS ENTRIES UPON ERROR
>
> 2016-05-24 19:59:17.247 1879 ERROR oslo_messaging.rpc.dispatcher   File 
> "/usr/lib/python2.7/dist-packages/cinder/openstack/common/scheduler/base_filter.py",
>  line 43, in filter_all
> 2016-05-24 19:59:17.247 1879 ERROR oslo_messaging.rpc.dispatcher if 
> self._filter_one(obj, filter_properties):
> 2016-05

Re: [Openstack] [openstack][cinder][vmware] why can't snapshot attached volume

2016-08-01 Thread Erlon Cruz

Have tried with the --force option?

On Mon, Jul 25, 2016 at 8:12 AM, James Guo  wrote:

> Now when a volume is attached to a vm, we can't snapshot it.
>
> I think vCenter does't have similar limitation. So how about removing the
> limitation?
>
> ___
> 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] cinder-volume can not live migration

2018-06-01 Thread Erlon Cruz

Hi Cheung,

Can't figure out much from your logs. Its more likely to be an LVM thing.
We haven't tested this scenario, as the tests we run only tests 1GB volumes
for performace reasons. But why would someone create a volume bigger than
that? :P

Can you open a bug on launchpad? Describing the steps to reproduce.

Erlon

2018-02-22 23:30 GMT-03:00 Cheung 楊禮銓 :

> Dear:
>
> If the volume size is bigger than 50G, I can not live migration lvm volume.
>
> I am using openstack pike version.
>
> Do I miss something?
>
> [root@controller01: cinder]# cinder get-pools
> +--+--+
> | Property | Value|
> +--+--+
> | name | controller01@lvm#LVM-SAS |
> +--+--+
> +--+--+
> | Property | Value|
> +--+--+
> | name | controller02@lvm#LVM-SAS |
> +--+--+
>
>
> [root@controller01: cinder]# openstack volume show
> 1495b9e9-e56a-468b-a134-59b0a728fa00
> ++--+
> | Field  | Value|
> ++--+
> | attachments| []   |
> | availability_zone  | nova |
> | bootable   | false|
> | consistencygroup_id| None |
> | created_at | 2018-02-23T02:15:14.00   |
> | description|  |
> | encrypted  | False|
> | id | 1495b9e9-e56a-468b-a134-59b0a728fa00 |
> | migration_status   | error|
> | multiattach| False|
> | name   | windows  |
> | os-vol-host-attr:host  | controller01@lvm#LVM-SAS |
> | os-vol-mig-status-attr:migstat | error|
> | os-vol-mig-status-attr:name_id | None |
> | os-vol-tenant-attr:tenant_id   | 963097c754bf40c5a077f2ae89be36c3 |
> | properties |  |
> | replication_status | None |
> | size   | 51   |
> | snapshot_id| None |
> | source_volid   | None |
> | status | available|
> | type   | LVM-SAS  |
> | updated_at | 2018-02-23T02:18:47.00   |
> | user_id| 5bfa4f66825a40709e44a047bd251bcb |
> ++--+
>
>
>
>
>
>
> --
> 本電子郵件及其所有附件所含之資訊均屬機密，僅供指定之收件人使用，未經寄件人同意不得揭露、複製或散布本電子郵件。若您並非指定之收件人，請勿使用、
> 保存或揭露本電子郵件之任何部分，並請立即通知寄件人並完全刪除本電子郵件。網路通訊可能含有病毒，收件人應自行確認本郵件是否安全，若因此造成損害，寄件人恕不負責。
>
>
> The information contained in this communication and attachment is
> confidential and is intended only for the use of the recipient to which
> this communication is addressed. Any disclosure, copying or distribution of
> this communication without the sender's consents is strictly prohibited. If
> you are not the intended recipient, please notify the sender and delete
> this communication entirely without using, retaining, or disclosing any of
> its contents. Internet communications cannot be guaranteed to be
> virus-free. The recipient is responsible for ensuring that this
> communication is virus free and the sender accepts no liability for any
> damages caused by virus transmitted by this communication.
>
> ___
> 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] OpenStack 2014.1 ("Icehouse") is released !

Re: [Openstack] [openstack-dev] how and which tempest tests to run

Re: [Openstack] [Cinder] deploying multiple backend

Re: [Openstack] Cinder | Volume creation stuck in the "creating" status

Re: [Openstack] Cinder type-create error during Devstack installation

Re: [Openstack] Accelerating the Enterprise Adoption of OpenStack

Re: [Openstack] Cinder, custom filters and weighers.

Re: [Openstack] Cinder

Re: [Openstack] Cinder Multiple Backends - Filter On Tenant

Re: [Openstack] Fw: Re: Cinder Multiple Backends - Filter On Tenant

Re: [Openstack] Cinder Instance Locality Filter Error

Re: [Openstack] [openstack][cinder][vmware] why can't snapshot attached volume

Re: [Openstack] cinder-volume can not live migration

13 matches

Site Navigation

Mail list logo

Footer information