Thursday, 2015-11-19

« Wednesday, 2015-11-18 Index Friday, 2015-11-20 »
*** gouthamr has quit IRC00:05
*** bswartz has joined #openstack-manila00:08
*** rebase has quit IRC00:32
*** zhongjun2 has joined #openstack-manila00:44
*** zhongjun has quit IRC00:46
*** rebase has joined #openstack-manila00:59
*** leeantho has quit IRC01:15
*** merooney has quit IRC01:16
*** jasonsb has quit IRC01:22
*** akshai has quit IRC01:27
*** jasonsb has joined #openstack-manila01:53
*** gouthamr has joined #openstack-manila01:55
*** jasonsb has quit IRC01:56
*** gouthamr_ has joined #openstack-manila02:15
*** gouthamr has quit IRC02:18
*** openstack has joined #openstack-manila02:26
*** haomaiwang has joined #openstack-manila02:29
*** absubram has quit IRC02:30
*** haomaiwang has quit IRC02:38
*** haomaiwa_ has joined #openstack-manila02:39
*** akshai has quit IRC02:49
*** rebase has quit IRC03:14
*** gouthamr_ has quit IRC03:30
*** rushil has joined #openstack-manila03:56
openstackgerritzhongjun proposed openstack/manila: QoS support for shares  https://review.openstack.org/24728603:56
*** lpabon has quit IRC04:03
*** bill_az has quit IRC04:10
*** rushil has quit IRC04:13
*** jasonsb has joined #openstack-manila05:04
*** rushil has joined #openstack-manila05:10
*** jasonsb has quit IRC05:20
*** houming-wang has joined #openstack-manila05:21
*** jasonsb has joined #openstack-manila05:46
*** jasonsb has quit IRC06:30
*** rushil has quit IRC06:34
*** jasonsb has joined #openstack-manila06:38
*** jasonsb has quit IRC06:50
*** jasonsb has joined #openstack-manila06:52
*** dalgaaf has joined #openstack-manila06:56
*** jasonsb has quit IRC06:57
*** breitz has quit IRC07:01
*** breitz has joined #openstack-manila07:01
*** shausy has joined #openstack-manila07:21
openstackgerritzhongjun proposed openstack/manila: Do not allow to modify access for public share type  https://review.openstack.org/21921307:33
openstackgerritzhongjun proposed openstack/manila: Do not allow to modify access for public share type  https://review.openstack.org/21921307:38
*** rushil has joined #openstack-manila07:46
*** jvarlamova has quit IRC07:50
*** rushil has quit IRC07:54
openstackgerritzhongjun proposed openstack/manila: QoS support for shares  https://review.openstack.org/24728608:13
openstackgerritzhongjun proposed openstack/manila: QoS support for shares  https://review.openstack.org/24728608:16
*** lpetrut has joined #openstack-manila08:19
*** jvarlamova has joined #openstack-manila08:19
openstackgerritzhongjun proposed openstack/manila: Do not allow to modify access for public share type  https://review.openstack.org/21921308:36
*** shausy has quit IRC08:49
zhongjun22ameade, bswartz: ping08:52
zhongjun22ameade, bswartz: After we were discussed about qos in IRC meeting, I put some description(about qos) in the doc(link: https://review.openstack.org/#/c/247286/), Could you use the doc review to register feedback, and make the qos feature go on.08:53
*** deepakcs has joined #openstack-manila08:53
*** shausy has joined #openstack-manila08:55
*** shausy has quit IRC08:57
*** haomaiwa_ has quit IRC08:57
*** haomaiwang has joined #openstack-manila08:59
*** lgreg has quit IRC08:59
*** lgreg has joined #openstack-manila09:00
*** shausy has joined #openstack-manila09:00
*** haomaiwang has quit IRC09:01
*** haomaiwang has joined #openstack-manila09:01
*** lpetrut has quit IRC09:18
*** abhi has quit IRC09:49
openstackgerritValeriy Ponomaryov proposed openstack/manila: Improve Tempest tests for consistency groups  https://review.openstack.org/24705209:51
*** haomaiwang has quit IRC10:01
*** houming-wang has quit IRC10:01
*** openstackgerrit has quit IRC10:01
*** haomaiwang has joined #openstack-manila10:01
*** openstackgerrit has joined #openstack-manila10:01
*** abhi has joined #openstack-manila10:11
*** openstack has joined #openstack-manila10:19
openstackgerritEmilien Macchi proposed openstack/puppet-manila: Acceptance: use common bits from puppet-openstack-integration  https://review.openstack.org/24740110:28
*** lpetrut has joined #openstack-manila10:41
*** tpsilva has joined #openstack-manila10:59
*** haomaiwang has quit IRC11:01
*** logan2 has quit IRC11:01
*** haomaiwang has joined #openstack-manila11:01
*** logan2 has joined #openstack-manila11:01
*** ekarlso has quit IRC11:05
*** ociuhandu has quit IRC11:17
*** ociuhandu has joined #openstack-manila11:25
*** eduardo_ has joined #openstack-manila11:26
*** ociuhandu has quit IRC11:26
*** ekarlso has joined #openstack-manila11:30
openstackgerritValeriy Ponomaryov proposed openstack/manila: Improve Tempest tests for consistency groups  https://review.openstack.org/24705211:30
openstackgerritSilvan Kaiser proposed openstack/manila: Implements ensure_share() in Quobyte driver  https://review.openstack.org/23968611:41
openstackgerritSilvan Kaiser proposed openstack/manila: Add share id to Quobyte backend volume name  https://review.openstack.org/24167111:43
openstackgerritzhongjun proposed openstack/manila: QoS support for shares  https://review.openstack.org/24728611:46
*** deepakcs has quit IRC11:50
*** haomaiwang has quit IRC12:01
*** haomaiwang has joined #openstack-manila12:01
*** martyturner has joined #openstack-manila12:07
*** ociuhandu has joined #openstack-manila12:12
*** vkmc-afk is now known as vkmc12:22
*** vkmc is now known as vkmc-afk12:26
*** vkmc-afk is now known as vkmc12:27
*** martyturner has quit IRC12:34
gansobswartz: ping12:36
*** houming-wang has joined #openstack-manila12:54
*** akerr_away is now known as akerr_12:55
*** akerr_ has quit IRC12:55
*** haomaiwang has quit IRC13:01
*** shausy has quit IRC13:01
*** haomaiwang has joined #openstack-manila13:01
*** gouthamr has joined #openstack-manila13:11
gouthamrkaisers: ping13:18
*** vkmc is now known as vkmc-afk13:21
*** openstackstatus has joined #openstack-manila13:34
*** ChanServ sets mode: +v openstackstatus13:34
openstackgerritValeriy Ponomaryov proposed openstack/manila: Improve Tempest tests for consistency groups  https://review.openstack.org/24705213:34
*** zhongjun2 has joined #openstack-manila13:37
*** akerr has joined #openstack-manila13:38
*** zhongjun22 has quit IRC13:40
bswartzganso: I'll be in the office soon, ping me when I'm back online13:44
*** bswartz has quit IRC13:44
*** haomaiwang has quit IRC13:45
*** porrua has joined #openstack-manila13:48
*** eharney has quit IRC13:54
*** xyang1 has joined #openstack-manila13:54
kaisersgouthamr: hi!13:58
kaisersnidhimittalhada: Hi! Sry but i saw your msg too late!13:59
kaisersgouthamr: I'll be afk in a min but back on later for the manila meeting...14:00
*** akshai has joined #openstack-manila14:06
*** dustins has joined #openstack-manila14:07
*** timcl has quit IRC14:13
*** haomaiwang has joined #openstack-manila14:15
*** bswartz has joined #openstack-manila14:18
*** merooney has joined #openstack-manila14:21
openstackgerritJohn Spray proposed openstack/manila: share: add access_key to instance mapping  https://review.openstack.org/24754014:24
*** haomai___ has joined #openstack-manila14:31
*** haomaiwang has quit IRC14:34
*** cknight has joined #openstack-manila14:34
*** houming-wang has quit IRC14:44
*** markstur_ has joined #openstack-manila14:45
*** houming-wang has joined #openstack-manila14:46
*** sghatty_ has quit IRC14:47
*** vkmc-afk is now known as vkmc14:50
*** juzuluag has joined #openstack-manila14:51
*** houming-wang has quit IRC14:56
*** juzuluag has quit IRC14:56
*** houming-wang has joined #openstack-manila14:59
*** breitz has quit IRC15:00
*** haomai___ has quit IRC15:01
gansobswartz: just got back15:01
vponomaryovmarkstur: weekly meeting?15:01
*** haomaiwang has joined #openstack-manila15:01
gansobswartz: was going to ask if there is a better host for images, google drive is blocked in china15:01
*** a_ta has joined #openstack-manila15:03
*** timcl has joined #openstack-manila15:04
*** jasonsb has joined #openstack-manila15:04
*** breitz has joined #openstack-manila15:04
*** sghatty_ has joined #openstack-manila15:06
*** sgotliv has quit IRC15:09
*** eharney has joined #openstack-manila15:13
*** dustins has quit IRC15:13
*** breitz has quit IRC15:15
*** sgotliv has joined #openstack-manila15:16
*** Zhongjun has joined #openstack-manila15:19
*** haomaiwang has quit IRC15:21
*** vkmc has quit IRC15:24
*** rushil has joined #openstack-manila15:25
*** houming-wang has quit IRC15:28
*** rushil has quit IRC15:30
*** vkmc has joined #openstack-manila15:33
*** alyson_ has joined #openstack-manila15:33
*** marcusvrn_ has joined #openstack-manila15:33
*** JoseMello has joined #openstack-manila15:38
*** ayma has joined #openstack-manila15:43
openstackgerritOpenStack Proposal Bot proposed openstack/manila: Updated from global requirements  https://review.openstack.org/24609515:46
openstackgerritOpenStack Proposal Bot proposed openstack/manila-ui: Updated from global requirements  https://review.openstack.org/24760715:46
*** nkrinner has quit IRC15:46
*** nkrinner has joined #openstack-manila15:47
openstackgerritOpenStack Proposal Bot proposed openstack/python-manilaclient: Updated from global requirements  https://review.openstack.org/24715615:52
*** houming-wang has joined #openstack-manila15:54
*** leeantho has joined #openstack-manila16:00
openstackgerritOpenStack Proposal Bot proposed openstack/python-manilaclient: Updated from global requirements  https://review.openstack.org/24715616:01
bswartzover here guys16:01
* ganso moves over16:01
*** zhongjun22 has joined #openstack-manila16:01
gouthamrganso: you have the stage16:02
bswartzvponomaryov xyang1 gouthamr cknight ganso markstur_ jayxu16:02
xyang1hi16:02
*** casusbelli has joined #openstack-manila16:02
gansowe were still discussing deadlines16:02
bswartzI think the deadline discussion pretty much wrapped up16:03
gansook16:03
bswartzI didn't hear any opposition16:03
gansoso... #link https://drive.google.com/file/d/0B30HPZmaePCHMlAzcjJlYm5rRTA/view?usp=sharing16:03
bswartzI will compose an ML post describing what we agreed to16:03
bswartz(or what I think we agreed to)16:03
gansothat are 4 images in that link16:03
gansothat represents connecting Data Copy Service Node to Share servers in DHSS = True mode16:04
gansothe first one is the problem16:04
bswartzganso: the image is super tiny16:04
gansothe other 3 below are my suggestions16:04
gansobswartz: sorry, can you download and zoom in?16:04
bswartzthere we go16:04
bswartzyes downloading works16:04
bswartzokay 1 sec while I read this image16:05
vponomaryovganso: you have 50 inches monitor? ))16:05
gansovponomaryov: lol no16:05
gansomy first suggestion is having a network for the data copy node that interconnects all share server networks16:06
gansoso there would only need to be one connection between the data copy service node to that network16:06
gansomy 2nd suggestion is for each share server, during setup_server method, drivers would create an additional VIF16:07
bswartzganso: I'm not sure I agree with the first picture16:07
bswartzit may be accurate for the generic driver, but not all share-server drivers look like that16:07
gansobswartz: yes... I am modeled it based on generic driver16:08
*** casusbelli has quit IRC16:08
gansobswartz: I *modeled16:08
bswartzganso: in parcular the presence of the "routers" in the picture is contrary to recommended practice16:08
vponomaryovagree, other drivers use API for talking to backend, not CLI16:08
bswartzand the VIF connection for management is also unusual16:09
bswartzbut if we ignore those details and focus on differences between 1 and 2-416:09
gansothe generic driver uses a VIF to connect the manila-share node to the share server in order to issue SSH commands16:09
gansobswartz: yes, precisely16:09
bswartzthen I think 4 comes closest to what I have been thinking about16:09
vponomaryovganso: better to design it exactly not based on generic driver16:10
gansothe most important thing is for the data copy service node to mount the share that is exported for VMs16:10
gansoI always believed what the generic driver does was the best practice16:11
gansobecause it attemps to segregate networks and access16:11
bswartzganso: do you have any pros/cons for these different approaches?16:11
vponomaryovganso: it is too different compared to all other16:11
gansothe main concern here what I am not familiar with the answer, is that anything related to VIF relies on Neutron node16:11
bswartzthe generic driver matches the model used by other share-server drivers, but due to limitations in nova and neutron it has to do some awkward things16:11
vponomaryovvariant 4 looks the best16:12
bswartzI think that 3 simply won't work for real hardware16:12
gansolike, I suspect that for creating a VIF in the data copy service node, the service would need to be running in the neutron node16:12
bswartzand 2 seems like a more complicated approach to get the same effect as 416:13
gansoif someone can confirm that, then we can forget about pictures 2 and 316:13
bswartzthe reason I like 4 is that there are other benefits16:13
bswartzfor example the nova-share-attach stuff redhat is proposing will need something like 4 to attach shares on share-server drivers to guests through the hypervisor16:13
gansobswartz: agreed, the main benefit of 4 is that the admin may want to mount shares to perform maintenance... creating a VM just for that is more hassle16:14
bswartzvponomaryov: can we make the generic driver do 4?16:14
vponomaryovbswartz: yes, also, there were some plans in Neutron to provide admin net16:14
vponomaryovbswartz: remember such disscussion logn time ago?16:15
bswartzso to go a little deeper into the proposed implementation16:15
vponomaryovbswartz: with one note - admin net for neutron, not nova network16:15
gansobswartz: I did not realize you needed admin network for that use case you mentioned16:15
bswartzthe way I think this needs to work is that when creating a share server, the share server requests a number of IP addresses from the manager for guest network access, and I think it will need to now also request a number of IP addresses from the manager for admin network access16:15
gansovponomaryov: we agreed to deprecate nova network16:16
gansobswartz: share servers with 2 IPs, right?16:16
gansobswartz: for each share server16:16
bswartzthe administrator will need to setup a network plugin using one of the existing plugins to represent the "admin" network16:16
bswartzbecause something will need to control provisioning of IPs on the admin network16:17
bswartzI think the standalone of neutron-single-network plugin could both be used for that function16:17
gansobswartz: yes, that was another point I was going to get into... this setup has to be automatic... DHSS = true drivers should not need administrator intervention16:17
bswartzstandalone or neutron-single-network plugin16:17
bswartzwell the administrator is going to have to establish a pool of IPs for use by share servers on the admin network16:18
bswartzthat should ideally be a one-time step at the beginning16:18
gansobswartz: if it is a one-time only configuration, seems ok16:18
bswartzokay so the manager will have 2 network plugins for every driver with share-servers16:19
bswartzone network plugin for guest networks and 1 network plugin for the admin network (which will always be flat)16:19
gansobswartz: are you sure it can always be flat?16:20
bswartzand the driver will need to request IPs from both16:20
bswartzganso: the admin network is flat by definition16:20
gansobswartz: AFAIK, Suse cloud setup uses vlan for admin network16:20
bswartzif you segment your admin network then things can't talk to eachother16:20
bswartzhow many vlans does it use?16:21
gansobswartz: I am not 100% sure16:21
gansobswartz: just a few, tagged VLAN16:21
bswartzif it just uses 1 vlan, then it's still flat16:21
vponomaryovsummon toabctl16:21
gansobswartz: yes, all admin nodes are in the same VLAN16:21
toabctlvponomaryov: ?16:21
bswartzif people are using multiple vlans for the admin network, then I agree with have a challenge16:21
bswartzwe* have a challenge16:22
vponomaryovtoabctl: does Suse use vlans for admin net?16:22
vponomaryovtoabctl; 10 comments above16:22
*** zhongjun22 has quit IRC16:22
* ganso hear crickets16:24
bswartzpatience...16:24
bswartztoabctl might not know16:24
toabctlbswartz: just reading the backlog.16:25
vponomaryov"what a huge requests have you guys" said DataBase and hang out forever ))16:25
gansovponomaryov: lol16:26
toabctlso afaik we support VLANs for the admin network16:27
bswartztoabctl: a single VLAN or multiple?16:27
toabctlbut not sure if multiple vlans are supported. I need to check that16:27
toabctlbswartz: ^^16:27
bswartztoabctl: and if multiple, then how do you talk between them?16:27
bswartzok16:27
*** houming-wang has quit IRC16:27
gansoI am booting my Suse right now lol16:27
*** houming-wang has joined #openstack-manila16:29
toabctlbswartz: so seems that in the config file you can set a single vlan16:29
toabctlI'll ask somebody16:30
*** houming-wang has left #openstack-manila16:30
bswartzganso: well we need to ensure that the mechanism for giving network resources to share servers on the admin network is flexible enough to support how people actually configure their admin networks16:31
*** markstur_ has quit IRC16:31
gansoif the admin network is using VLANs, and the driver needs a neutron plugin, that can be either VLAN or FLAT, can't that be configurable?16:31
bswartzganso: it's a question of what needs to be provided in addition to the IP, netmask, gateway16:31
bswartzif we need a segmentation type and segmentation ID then that's something we need to take into account16:32
bswartzI think a manila network plugin can provide all of those things16:32
*** houming has joined #openstack-manila16:32
gansoAFAIK, the plugin will create a network with the given parameters, create a network and attach it to a router, right?16:33
bswartzeven the flat network plugins can provide those things, right vponomaryov?16:33
bswartzif you use the single-neutron-network plugin, it can return a segmentation type and ID if the neutron network has those16:33
toabctlso I double checked and the admin net must be native (no vlans)16:33
bswartztoabctl: good to know16:34
gansotoabctl: great!16:34
gansook so we decided on picture 4, right? maybe I need to work on a design following that approach decision, like what drivers will need to do and what plugins will be available16:35
bswartzganso: yes16:35
bswartzganso: we just need to make the manager read another config variable when it has a share-network driver16:36
bswartzand the manager needs a bunch of code to handle the admin network16:36
*** houming has quit IRC16:37
gansohummmmmm16:37
bswartzmuch of that code would be similar to the existing network handling code16:38
bswartzwhen creating a share server, the driver requests IPs, and the manager provides them16:38
bswartzbut we need to keep the "tenant" IPs and the "admin" IPs separate16:38
gansobut driver responsibilities will be only setting a flag and receiving an IP, and using that IP to export the share in that network as well, right?16:41
gansoflag = config variable16:41
bswartzso the flag that matters is DHSS=true16:44
bswartzall drivers with that flag will need to return the number of admin IPs they need per share server, and the manager should provide those IPs similar to how it provides tenant facing IPs16:44
bswartzthe driver will be expected to know the difference between tenant and admin IPs ,and when creating export locations to tag the admin export locations as admin only (using export location metadata)16:45
gansobswartz: we are agreeing that it will be standard as well... like a minimum requirement? it will affect all existing drivers that implement DHSS = true16:46
gansobswartz: nice way of using export location metadata :)16:46
bswartzyes this will need to become a required feature asap16:47
bswartzbecause migration cannot work without it16:47
gansobswartz: yes16:47
*** nkrinner has quit IRC16:50
*** a_ta has quit IRC16:51
*** a_ta has joined #openstack-manila16:51
*** a_ta has quit IRC16:56
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Refactor authorize() method in wsgi.py  https://review.openstack.org/24655516:56
gouthamrvponomaryov: Thanks for your comments. Pushed this back up ^^ .. Would love to get this fix in asap to avoid the churn with newer APIs that would want to use it..17:03
*** a_ta has joined #openstack-manila17:03
vponomaryovbswartz: neutron network plugin will provide such info. StandAlone network plugin does have "segmentation ID", but not "network type"17:10
bswartzvponomaryov: I mean segmentation type (i.e. vlan, vxlan, etc.)17:11
vponomaryovbswartz: right17:12
vponomaryovbswartz: so, if this one is required, then StandAlone network plugin should be updated17:13
vponomaryovbswartz: update is really small17:14
bswartzyou mean standalone network plugin doesn't currently provide segmentation type?17:15
bswartzthat seems like a bug17:15
vponomaryovyes17:16
vponomaryovit doesn't and it is bug17:16
bswartzk17:16
vponomaryovI can fix it right now17:16
vponomaryovbswartz: https://bugs.launchpad.net/manila/+bug/151798717:18
openstackLaunchpad bug 1517987 in Manila "standalone network plugin does not allow to setup network type" [Undecided,New]17:18
*** akshai has quit IRC17:28
openstackgerritValeriy Ponomaryov proposed openstack/manila: Add support of 'network_type' to standalone network plugin  https://review.openstack.org/24769817:35
vponomaryovbswartz: ^17:35
*** adrianofr has quit IRC17:36
bswartzvponomaryov: I like "segmentation_type" more than network_type17:37
vponomaryovbswartz: it is part of share_network model17:37
vponomaryovbswartz: also, Neutron uses "network_type"17:37
vponomaryovbswartz: liberty-backport-potential?17:38
bswartzyes we could backport this17:38
bswartzafter proper testing17:38
vponomaryovbswartz: each conf opt has default value as None17:39
bswartzso what gets set today? is it none when the driver sees it?17:41
vponomaryovbswartz: in which case?17:42
bswartzvponomaryov: also we need validation of the input -- so someone can not set network type to "blahblah"17:42
bswartzperhaps negative test too17:43
vponomaryovbswartz: it is up to the driver17:43
bswartzdrivers are expected to validate the option?17:43
bswartzthat will probably result in duplicate validation code17:43
vponomaryovbswartz: I mean each driver can support any netwrok type and any can be setup17:44
bswartzseems better to validate it in one place17:44
bswartzI know some drivers may support a subset of the valid options, but completely invalid choices should be rejected in a central place17:44
*** dustins has joined #openstack-manila17:45
gansobswartz +117:45
vponomaryovbswartz: https://github.com/openstack/manila/blob/4c265c4f/manila/share/manager.py#L128917:45
vponomaryovbswartz: so, it is ok already17:45
*** dustins has quit IRC17:46
bswartzthis won't reject invalid network types, it will only reject invalid segmentation ids, assuming the network type is in [None, 'flat', 'vlan', 'vxlan', 'gre']17:47
bswartza network type of "blahblah" will pass this check regardless of the segmentation id17:47
*** Zhongjun has quit IRC17:47
openstackgerritValeriy Ponomaryov proposed openstack/manila: Add support of 'network_type' to standalone network plugin  https://review.openstack.org/24769817:48
vponomaryovbswartz: so, you propose to add check into plugin itself?17:49
bswartzyes17:49
vponomaryovbswartz: because in case of neutron it is autodiscovered17:49
bswartzneutron does its own sanity checking on the values17:49
bswartzit's safer to trust what neutron tells us17:49
bswartzusers could easily put garbage in manila conf file though17:49
bswartzif we don't check it in the manila plugin, the error will depend on the driver's own checks17:50
vponomaryovbswartz: agree, will add validation17:50
vponomaryovbswartz: revert back name of the bug - https://bugs.launchpad.net/manila/+bug/1517987 ?17:51
openstackLaunchpad bug 1517987 in Manila "Standalone network plugin does not allow to set segmentation type" [High,In progress] - Assigned to Valeriy Ponomaryov (vponomaryov)17:51
bswartzsure the bug name doesn't matter so much17:52
bswartzI didn't realize "network_type" was already hardcoded in so many places17:52
*** gouthamr has quit IRC17:54
*** breitz has joined #openstack-manila17:58
*** sghatty_ has quit IRC18:01
*** eduardo_ has quit IRC18:02
*** dustins has joined #openstack-manila18:05
*** dustins has quit IRC18:10
*** lpetrut has quit IRC18:18
*** a_ta has quit IRC18:19
*** a_ta has joined #openstack-manila18:19
*** dcain has joined #openstack-manila18:22
*** a_ta has quit IRC18:24
*** akshai has joined #openstack-manila18:27
*** gouthamr has joined #openstack-manila18:27
akshairhefner: you around?18:28
rhefnerakshai: what's up?18:29
akshairhefner: hope you're well. i have this packstack install issue. Execution of '/usr/bin/nova network-create novanetwork --fixed-range-v4 192.168.32.0/22' returned 1: ERROR (CommandError): You must provide a username or user id via --os-username, --os-user-id, env[OS_USERNAME] or env[OS_USER_ID]18:31
akshairhefner: note that it is looking for a username. The username or userid must be specified for the command to execute. But, shouldn't packstack should do this for me?? we get the keystonerc file only after packstack finishes install.18:32
gouthamrakshai: this looks like an rdo question, not manila related.18:32
*** sghatty_ has joined #openstack-manila18:33
akshairhefner: we can switch over to #rdo?18:33
rhefnerakshai: ack18:34
*** ociuhandu has quit IRC18:34
*** dustins has joined #openstack-manila18:36
*** dustins has quit IRC18:38
*** dustins has joined #openstack-manila18:42
*** david-lyle has quit IRC18:48
*** lpetrut has joined #openstack-manila19:04
*** dustins has quit IRC19:09
*** JoseMello has quit IRC19:14
*** jasonsb has quit IRC19:22
*** a_ta has joined #openstack-manila19:23
*** akshai has quit IRC19:26
*** ociuhandu has joined #openstack-manila19:32
*** akshai has joined #openstack-manila19:34
*** alyson_ has quit IRC19:37
*** david-lyle has joined #openstack-manila19:43
openstackgerritGoutham Pacha Ravi proposed openstack/manila: [WIP] Share Replication API and Scheduler Support  https://review.openstack.org/23857219:44
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Add functional tests for Manila share replication  https://review.openstack.org/24484319:44
*** openstackgerrit has quit IRC19:46
*** openstackgerrit has joined #openstack-manila19:47
*** lpetrut has quit IRC19:52
*** timcl1 has joined #openstack-manila19:59
*** timcl has quit IRC20:00
*** rushil has joined #openstack-manila20:11
*** rebase has joined #openstack-manila20:29
*** timcl1 has quit IRC20:30
*** rebase has quit IRC20:31
*** timcl has joined #openstack-manila20:32
*** tpsilva has quit IRC20:51
*** ayma1 has joined #openstack-manila20:53
*** ayma has quit IRC20:55
*** timcl has quit IRC21:04
*** timcl has joined #openstack-manila21:05
*** merooney has quit IRC21:09
*** timcl has quit IRC21:13
*** abhi has quit IRC21:13
*** timcl has joined #openstack-manila21:13
*** a_ta has quit IRC21:15
*** rhagarty has quit IRC21:15
*** a_ta has joined #openstack-manila21:16
*** rhagarty has joined #openstack-manila21:17
*** a_ta has quit IRC21:17
*** a_ta has joined #openstack-manila21:17
*** zhongjun2 has quit IRC21:17
*** zhongjun has joined #openstack-manila21:18
*** a_ta has quit IRC21:29
*** a_ta has joined #openstack-manila21:30
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Share Replication API and Scheduler Support  https://review.openstack.org/23857221:30
openstackgerritGoutham Pacha Ravi proposed openstack/manila: Add functional tests for Manila share replication  https://review.openstack.org/24484321:30
*** a_ta_ has joined #openstack-manila21:32
*** rhagarty has quit IRC21:34
*** a_ta has quit IRC21:34
*** zhongjun has quit IRC21:36
*** rhagarty has joined #openstack-manila21:36
*** zhongjun has joined #openstack-manila21:37
*** sgotliv has quit IRC21:39
*** jasonsb has joined #openstack-manila21:40
*** jasonsb has quit IRC21:45
*** akerr has quit IRC21:46
*** rushil has quit IRC21:57
*** lpetrut has joined #openstack-manila21:58
*** bswartz has quit IRC22:02
*** a_ta_ has quit IRC22:02
*** a_ta has joined #openstack-manila22:03
*** a_ta has quit IRC22:08
*** a_ta has joined #openstack-manila22:10
*** a_ta has quit IRC22:11
*** a_ta has joined #openstack-manila22:12
*** eharney has quit IRC22:15
*** porrua has quit IRC22:15
*** a_ta_ has joined #openstack-manila22:17
*** a_ta has quit IRC22:17
*** ganso has quit IRC22:18
*** zhongjun2 has joined #openstack-manila22:20
*** a_ta_ has quit IRC22:20
*** zhongjun has quit IRC22:21
*** dcain has quit IRC22:26
*** abhi has joined #openstack-manila22:27
*** lpetrut has quit IRC22:28
*** a_ta has joined #openstack-manila22:29
*** gouthamr has quit IRC22:45
*** pgbridge has joined #openstack-manila22:54
*** erlon has quit IRC22:59
*** breitz has quit IRC22:59
*** a_ta has quit IRC23:04
*** a_ta has joined #openstack-manila23:05
*** a_ta has quit IRC23:10
*** logan2 has quit IRC23:10
*** logan2 has joined #openstack-manila23:10
*** toabctl has quit IRC23:11
*** toabctl has joined #openstack-manila23:13
*** rhagarty_ has joined #openstack-manila23:18
*** rhagarty has quit IRC23:20
csabacknight: ping23:22
cknightcsaba: pong23:22
csabacknight: I answered your question in https://review.openstack.org/229830, pls ping me back if the input is OK with you in light of that or you have a better idea.23:25
cknightcsaba: thanks, will do23:26
*** darrenc is now known as darrenc_afk23:33
*** ayma1 has quit IRC23:34
*** leeantho has quit IRC23:34
*** cknight has quit IRC23:34
*** leeantho has joined #openstack-manila23:35
*** darrenc_afk is now known as darrenc23:56
« Wednesday, 2015-11-18 Index Friday, 2015-11-20 »

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!