Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
Looks like there is a short cut if you know the datastore version and you want to look it up. Exist today in the code: /datastores/datastore/versions/version /datastores/versions/version Add these paths: /datastores/datastore/versions/version/parameters /datastores/datastore/versions/version/parameters/parameters /datastores/versions/version/parameters /datastores/versions/version/parameters/parameters This would the new set of paths for the parameters. Any objections? On Fri, Jan 24, 2014 at 2:47 PM, Craig Vyvial cp16...@gmail.com wrote: Oh shoot. That reminds me i needed to rebase the code i was working on. And yes this changes things a little because we are using the same template paths for the validation_rules as the base template which uses the manager field on the datastore_version. This means that we need to make the path over the version instead. /datastores/datastore/versions/version/parameters /datastores/datastore/versions/version/parameters/parameters Thanks for reminding me Morris. -Craig On Thu, Jan 23, 2014 at 11:52 PM, Daniel Morris daniel.mor...@rackspace.com wrote: Quick question… When y'all say that onfiguration set must be associated to exactly one datastore, do you mean datastore or datastore version? Wouldn't the configuration set available parameters defaults need to be a unique 1-1 mapping to a datastore version as they will vary across versions not just the datastore type. You may have a configurable parameter that exists in MySQL 5.6 that does not exist in MySQL 5.1 or vice versa. Or am I misunderstanding? Thanks, Daniel From: Craig Vyvial cp16...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: Thursday, January 23, 2014 10:55 AM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores I support the latest as well. I will make it so. Thanks On Thu, Jan 23, 2014 at 8:16 AM, Daniel Salinas imsplit...@gmail.comwrote: I agree. This keeps everything identical to our current routing scheme. On Jan 23, 2014 7:31 AM, Denis Makogon dmako...@mirantis.com wrote: +1 to Greg. Given schema is more preferable for API routes /datastores/datastore/parameters /datastores/datastore/parameters/parameters 2014/1/23 Greg Hill greg.h...@rackspace.com To be more consistent with other APIs in trove, perhaps: /datastores/datastore/parameters /datastores/datastore/parameters/parameters Greg On Jan 22, 2014, at 4:52 PM, Kaleb Pomeroy kaleb.pome...@rackspace.com wrote: I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom -- *From:* Craig Vyvial [cp16...@gmail.com] *Sent:* Wednesday, January 22, 2014 4:11 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
Denis, This was slightly modified. https://blueprints.launchpad.net/trove/+spec/move-manager-to-datastore-version So an instance is correlated one-to-one with a datastore version because we need to the datastore manager to get the templates and the configuration rules because they are located in the same place. The manager can be shared among multiple versions but it could be unique for a version as well which could prove to be useful for version of mysql and other datastores. I hope this make sense. :) Thanks, Craig On Fri, Jan 24, 2014 at 3:29 PM, Denis Makogon dmako...@mirantis.comwrote: Hello, Craig. This short-cut seems like would affect initial design and implementation. For now we're pinning configuration to datastore (means for all version). I'd suggest you to elaborate how route changing would change current validations taking into accout version particular qualities. Best regards, Denis Makogon. 2014/1/24 Craig Vyvial cp16...@gmail.com Looks like there is a short cut if you know the datastore version and you want to look it up. Exist today in the code: /datastores/datastore/versions/version /datastores/versions/version Add these paths: /datastores/datastore/versions/version/parameters /datastores/datastore/versions/version/parameters/parameters /datastores/versions/version/parameters /datastores/versions/version/parameters/parameters This would the new set of paths for the parameters. Any objections? On Fri, Jan 24, 2014 at 2:47 PM, Craig Vyvial cp16...@gmail.com wrote: Oh shoot. That reminds me i needed to rebase the code i was working on. And yes this changes things a little because we are using the same template paths for the validation_rules as the base template which uses the manager field on the datastore_version. This means that we need to make the path over the version instead. /datastores/datastore/versions/version/parameters /datastores/datastore/versions/version/parameters/parameters Thanks for reminding me Morris. -Craig On Thu, Jan 23, 2014 at 11:52 PM, Daniel Morris daniel.mor...@rackspace.com wrote: Quick question… When y'all say that onfiguration set must be associated to exactly one datastore, do you mean datastore or datastore version? Wouldn't the configuration set available parameters defaults need to be a unique 1-1 mapping to a datastore version as they will vary across versions not just the datastore type. You may have a configurable parameter that exists in MySQL 5.6 that does not exist in MySQL 5.1 or vice versa. Or am I misunderstanding? Thanks, Daniel From: Craig Vyvial cp16...@gmail.com Reply-To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Date: Thursday, January 23, 2014 10:55 AM To: OpenStack Development Mailing List (not for usage questions) openstack-dev@lists.openstack.org Subject: Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores I support the latest as well. I will make it so. Thanks On Thu, Jan 23, 2014 at 8:16 AM, Daniel Salinas imsplit...@gmail.comwrote: I agree. This keeps everything identical to our current routing scheme. On Jan 23, 2014 7:31 AM, Denis Makogon dmako...@mirantis.com wrote: +1 to Greg. Given schema is more preferable for API routes /datastores/datastore/parameters /datastores/datastore/parameters/parameters 2014/1/23 Greg Hill greg.h...@rackspace.com To be more consistent with other APIs in trove, perhaps: /datastores/datastore/parameters /datastores/datastore/parameters/parameters Greg On Jan 22, 2014, at 4:52 PM, Kaleb Pomeroy kaleb.pome...@rackspace.com wrote: I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom -- *From:* Craig Vyvial [cp16...@gmail.com] *Sent:* Wednesday, January 22, 2014 4:11 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
To be more consistent with other APIs in trove, perhaps: /datastores/datastore/parameters /datastores/datastore/parameters/parameters Greg On Jan 22, 2014, at 4:52 PM, Kaleb Pomeroy kaleb.pome...@rackspace.commailto:kaleb.pome...@rackspace.com wrote: I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom From: Craig Vyvial [cp16...@gmail.commailto:cp16...@gmail.com] Sent: Wednesday, January 22, 2014 4:11 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.commailto:dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.commailto:mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
+1 to Greg. Given schema is more preferable for API routes /datastores/datastore/parameters /datastores/datastore/parameters/parameters 2014/1/23 Greg Hill greg.h...@rackspace.com To be more consistent with other APIs in trove, perhaps: /datastores/datastore/parameters /datastores/datastore/parameters/parameters Greg On Jan 22, 2014, at 4:52 PM, Kaleb Pomeroy kaleb.pome...@rackspace.com wrote: I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom -- *From:* Craig Vyvial [cp16...@gmail.com] *Sent:* Wednesday, January 22, 2014 4:11 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
I agree. This keeps everything identical to our current routing scheme. On Jan 23, 2014 7:31 AM, Denis Makogon dmako...@mirantis.com wrote: +1 to Greg. Given schema is more preferable for API routes /datastores/datastore/parameters /datastores/datastore/parameters/parameters 2014/1/23 Greg Hill greg.h...@rackspace.com To be more consistent with other APIs in trove, perhaps: /datastores/datastore/parameters /datastores/datastore/parameters/parameters Greg On Jan 22, 2014, at 4:52 PM, Kaleb Pomeroy kaleb.pome...@rackspace.com wrote: I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom -- *From:* Craig Vyvial [cp16...@gmail.com] *Sent:* Wednesday, January 22, 2014 4:11 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
I support the latest as well. I will make it so. Thanks On Thu, Jan 23, 2014 at 8:16 AM, Daniel Salinas imsplit...@gmail.comwrote: I agree. This keeps everything identical to our current routing scheme. On Jan 23, 2014 7:31 AM, Denis Makogon dmako...@mirantis.com wrote: +1 to Greg. Given schema is more preferable for API routes /datastores/datastore/parameters /datastores/datastore/parameters/parameters 2014/1/23 Greg Hill greg.h...@rackspace.com To be more consistent with other APIs in trove, perhaps: /datastores/datastore/parameters /datastores/datastore/parameters/parameters Greg On Jan 22, 2014, at 4:52 PM, Kaleb Pomeroy kaleb.pome...@rackspace.com wrote: I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom -- *From:* Craig Vyvial [cp16...@gmail.com] *Sent:* Wednesday, January 22, 2014 4:11 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Trove] how to list available configuration parameters for datastores
Hey everyone I have run into an issue with the configuration parameter URI. I'd like some input on what the URI might look like for getting the list configuration parameters for a specific datastore. Problem: Configuration parameters need to be selected per datastore. Currently: Its setup to use the default(mysql) datastore and this wont work for other datastores like redis/cassandra/etc. /configurations/parameters - parameter list for mysql /configurations/parameters/parameter_name - details of parameter We need to be able to request the parameter list per datastore. Here are some suggestions that outlines how each method may work. ONE: /configurations/parameters?datastore=mysql - list parameter for mysql /configurations/parameters?datastore=redis - list parameter for redis - we do not use query parameters for anything other than pagination (limit and marker) - this requires some finagling with the context to add the datastore. https://gist.github.com/cp16net/8547197 TWO: /configurations/parameters - list of datastores that have configuration parameters /configurations/parameters/datastore - list of parameters for datastore THREE: /datastores/datastore/configuration/parameters - list the parameters for the datastore FOUR: /datastores/datastore - add an href on the return to the configuration parameter list for the datastore /configurations/parameters/datastore - list of parameters for datastore FIVE: * Require a configuration be created with a datastore. Then a user may list the configuration parameters allowed on that configuration. /configurations/config_id/parameters - parameter list for mysql - after some thought i think this method (5) might be the best way to handle this. I've outlined a few ways we could make this work. Let me know if you agree or why you may disagree with strategy 5. Thanks, Craig Vyvial ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
I like #4 over #5 because it seems weird to have to create a configuration first to see what parameters are allowed. With #4 you could look up what is allowed first then create your configuration. Robert On Jan 22, 2014 10:18 AM, Craig Vyvial cp16...@gmail.com wrote: Hey everyone I have run into an issue with the configuration parameter URI. I'd like some input on what the URI might look like for getting the list configuration parameters for a specific datastore. Problem: Configuration parameters need to be selected per datastore. Currently: Its setup to use the default(mysql) datastore and this wont work for other datastores like redis/cassandra/etc. /configurations/parameters - parameter list for mysql /configurations/parameters/parameter_name - details of parameter We need to be able to request the parameter list per datastore. Here are some suggestions that outlines how each method may work. ONE: /configurations/parameters?datastore=mysql - list parameter for mysql /configurations/parameters?datastore=redis - list parameter for redis - we do not use query parameters for anything other than pagination (limit and marker) - this requires some finagling with the context to add the datastore. https://gist.github.com/cp16net/8547197 TWO: /configurations/parameters - list of datastores that have configuration parameters /configurations/parameters/datastore - list of parameters for datastore THREE: /datastores/datastore/configuration/parameters - list the parameters for the datastore FOUR: /datastores/datastore - add an href on the return to the configuration parameter list for the datastore /configurations/parameters/datastore - list of parameters for datastore FIVE: * Require a configuration be created with a datastore. Then a user may list the configuration parameters allowed on that configuration. /configurations/config_id/parameters - parameter list for mysql - after some thought i think this method (5) might be the best way to handle this. I've outlined a few ways we could make this work. Let me know if you agree or why you may disagree with strategy 5. Thanks, Craig Vyvial ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) /configurations/config_id/parameters (Option Five) + Smaller, canonical route to a configuration set - datastore/config relationshiop is much more ambiguous I'm planning on working a blueprint for this feature soon, so I'd like any feedback anyone has. - kpom From: Craig Vyvial [cp16...@gmail.com] Sent: Wednesday, January 22, 2014 10:10 AM To: OpenStack Development Mailing List Subject: [openstack-dev] [Trove] how to list available configuration parameters for datastores Hey everyone I have run into an issue with the configuration parameter URI. I'd like some input on what the URI might look like for getting the list configuration parameters for a specific datastore. Problem: Configuration parameters need to be selected per datastore. Currently: Its setup to use the default(mysql) datastore and this wont work for other datastores like redis/cassandra/etc. /configurations/parameters - parameter list for mysql /configurations/parameters/parameter_name - details of parameter We need to be able to request the parameter list per datastore. Here are some suggestions that outlines how each method may work. ONE: /configurations/parameters?datastore=mysql - list parameter for mysql /configurations/parameters?datastore=redis - list parameter for redis - we do not use query parameters for anything other than pagination (limit and marker) - this requires some finagling with the context to add the datastore. https://gist.github.com/cp16net/8547197 TWO: /configurations/parameters - list of datastores that have configuration parameters /configurations/parameters/datastore - list of parameters for datastore THREE: /datastores/datastore/configuration/parameters - list the parameters for the datastore FOUR: /datastores/datastore - add an href on the return to the configuration parameter list for the datastore /configurations/parameters/datastore - list of parameters for datastore FIVE: * Require a configuration be created with a datastore. Then a user may list the configuration parameters allowed on that configuration. /configurations/config_id/parameters - parameter list for mysql - after some thought i think this method (5) might be the best way to handle this. I've outlined a few ways we could make this work. Let me know if you agree or why you may disagree with strategy 5. Thanks, Craig Vyvial ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. signature.asc Description: Message signed with OpenPGP using GPGMail ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.comwrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom From: Craig Vyvial [cp16...@gmail.com] Sent: Wednesday, January 22, 2014 4:11 PM To: OpenStack Development Mailing List (not for usage questions) Subject: Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.commailto:dmako...@mirantis.com wrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.commailto:mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores
+1 yes that is true. Thanks, Craig On Wed, Jan 22, 2014 at 4:52 PM, Kaleb Pomeroy kaleb.pome...@rackspace.comwrote: I think that may have been a slight oversite. We will likely have the following two routes /datastores/datastore/configuration/ would be the collection of all parameters /datastores/datastore/configuration/:parameter would be an individual setting. - kpom -- *From:* Craig Vyvial [cp16...@gmail.com] *Sent:* Wednesday, January 22, 2014 4:11 PM *To:* OpenStack Development Mailing List (not for usage questions) *Subject:* Re: [openstack-dev] [Trove] how to list available configuration parameters for datastores Ok with overwhelming support for #3. What if we modified #3 slightly because looking at it again seems like we could shorten the path since /datastores/datastore/configuration doesnt do anything. instead of #1 /datastores/datastore/configuration/parameters maybe: #2 /datastores/datastore/parameters #3 /datastores/datastore/configurationparameters On Wed, Jan 22, 2014 at 2:27 PM, Denis Makogon dmako...@mirantis.comwrote: Goodday to all. #3 looks more than acceptable. /datastores/datastore/configuration/parameters. According to configuration parameters design, a configuration set must be associated to exactly one datastore. Best regards, Denis Makogon. 2014/1/22 Michael Basnight mbasni...@gmail.com On Jan 22, 2014, at 10:19 AM, Kaleb Pomeroy wrote: My thoughts so far: /datastores/datastore/configuration/parameters (Option Three) + configuration set without an associated datastore is meaningless + a configuration set must be associated to exactly one datastore + each datastore must have 0-1 configuration set + All above relationships are immediately apparent - Listing all configuration sets becomes more difficult (which I don't think that is a valid concern) +1 to option 3, given what kaleb and craig have outlined so far. I dont see the above minus as a valid concern either, kaleb. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
