https://wiki.openstack.org/w/api.php?action=feedcontributions&user=Sushilkm&feedformat=atomOpenStack - User contributions [en]2024-03-29T13:30:53ZUser contributionsMediaWiki 1.28.2https://wiki.openstack.org/w/index.php?title=Meetings/TroveMeeting&diff=87438Meetings/TroveMeeting2015-08-05T14:04:03Z<p>Sushilkm: /* Trove Meeting, Aug 5, 2015 */</p>
<hr />
<div>= Weekly Trove Team Meeting =<br />
<br />
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt<br />
<br />
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:<br />
<br />
==== Guidelines for Writing Clear Agenda Items ====<br />
An agenda item should have a clearly defined objective.<br />
<br />
* [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.<br />
* Bad: Discuss blueprint ‘xyz’<br />
* Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.<br />
<br />
<br />
When referring to previous conversations or competing viewpoints, be sure to summarize them.<br />
<br />
Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.<br />
<br />
== Trove Meeting, Aug 5, 2015 ==<br />
* Trove pulse update:<br />
** https://etherpad.openstack.org/p/trove-pulse-update<br />
<br />
* [sushilkm] Datastore registration spec open questions, https://review.openstack.org/188072<br />
** We talked a little about this in last week but want to bring this around to close on it. <br />
** Question which need to be answered to move on this spec. <br />
*** Should the api be simple CRUD operations on each object? (i.e. CRUD on datastores and versions separate) or make the API simplified where we really only care about the version when we update the image on an existing version or create a new version?<br />
** Thoughts from SlickNik and cp16net were there on last weeks agenda too, https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Meeting.2C_July_29.2C_2015,<br />
<br />
<br/><br />
[https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]<br />
<br/><br />
[http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Meetings/TroveMeeting&diff=87437Meetings/TroveMeeting2015-08-05T14:03:31Z<p>Sushilkm: /* Trove Meeting, Aug 5, 2015 */</p>
<hr />
<div>= Weekly Trove Team Meeting =<br />
<br />
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt<br />
<br />
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:<br />
<br />
==== Guidelines for Writing Clear Agenda Items ====<br />
An agenda item should have a clearly defined objective.<br />
<br />
* [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.<br />
* Bad: Discuss blueprint ‘xyz’<br />
* Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.<br />
<br />
<br />
When referring to previous conversations or competing viewpoints, be sure to summarize them.<br />
<br />
Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.<br />
<br />
== Trove Meeting, Aug 5, 2015 ==<br />
* Trove pulse update:<br />
** https://etherpad.openstack.org/p/trove-pulse-update<br />
<br />
* [sushilkm] Datastore registration spec open questions<br />
** We talked a little about this in last week but want to bring this around to close on it. <br />
** Question which need to be answered to move on this spec. <br />
*** Should the api be simple CRUD operations on each object? (i.e. CRUD on datastores and versions separate) or make the API simplified where we really only care about the version when we update the image on an existing version or create a new version?<br />
** Thoughts from SlickNik and cp16net were there on last weeks agenda too, https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Meeting.2C_July_29.2C_2015,<br />
<br />
<br/><br />
[https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]<br />
<br/><br />
[http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Meetings/TroveMeeting&diff=87436Meetings/TroveMeeting2015-08-05T14:01:37Z<p>Sushilkm: /* Trove Meeting, Aug 5, 2015 */</p>
<hr />
<div>= Weekly Trove Team Meeting =<br />
<br />
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt<br />
<br />
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:<br />
<br />
==== Guidelines for Writing Clear Agenda Items ====<br />
An agenda item should have a clearly defined objective.<br />
<br />
* [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.<br />
* Bad: Discuss blueprint ‘xyz’<br />
* Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.<br />
<br />
<br />
When referring to previous conversations or competing viewpoints, be sure to summarize them.<br />
<br />
Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.<br />
<br />
== Trove Meeting, Aug 5, 2015 ==<br />
* Trove pulse update:<br />
** https://etherpad.openstack.org/p/trove-pulse-update<br />
<br />
<br/><br />
[https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]<br />
<br/><br />
[http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]<br />
<br />
* [sushilkm] Datastore registration spec open questions<br />
** We talked a little about this in last week but want to bring this around to close on it. <br />
** Question which need to be answered to move on this spec. <br />
*** Should the api be simple CRUD operations on each object? (i.e. CRUD on datastores and versions separate) or make the API simplified where we really only care about the version when we update the image on an existing version or create a new version?<br />
** Thoughts from SlickNik and cp16net were there on last weeks agenda too, https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Meeting.2C_July_29.2C_2015,</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Meetings/TroveMeeting&diff=76257Meetings/TroveMeeting2015-03-25T05:34:10Z<p>Sushilkm: /* Trove Meeting, March 25, 2015 */</p>
<hr />
<div>= Weekly Trove Team Meeting =<br />
<br />
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt<br />
<br />
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:<br />
<br />
==== Guidelines for Writing Clear Agenda Items ====<br />
An agenda item should have a clearly defined objective.<br />
<br />
* [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.<br />
* Bad: Discuss blueprint ‘xyz’<br />
* Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.<br />
<br />
<br />
When referring to previous conversations or competing viewpoints, be sure to summarize them.<br />
<br />
Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.<br />
<br />
== Trove Meeting, March 25, 2015 ==<br />
<br />
* [SlickNik] Trove pulse update:<br />
** https://etherpad.openstack.org/p/trove-pulse-update<br />
* [vgnbkr] Instance Storage for Replication<br />
** https://etherpad.openstack.org/p/trove-replication-storage<br />
* [sushilkm] Different timeouts in configuration based per datastore<br />
** https://review.openstack.org/#/c/164640/<br />
<br />
== Trove Meeting, March 18, 2015 ==<br />
<br />
* [SlickNik] Trove pulse update:<br />
** https://etherpad.openstack.org/p/trove-pulse-update<br />
* [SlickNik] Openstack Feature Freeze this week for kilo-3:<br />
** https://launchpad.net/trove/+milestone/kilo-3<br />
** https://etherpad.openstack.org/p/TroveKilo3Blueprints<br />
* [SlickNik] Switch from oslo namespace packages to "oslo_" style modules<br />
** https://review.openstack.org/#/c/150709/ <br />
** For context please see: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059031.html<br />
*[peterstac] Come up with a strategy to deal with Mock()ing utility methods<br />
** We have several patchsets that are mocking execute_with_timeout, which can cause unexpected behaviour.<br />
** For context see: https://review.openstack.org/#/c/156486/ and https://review.openstack.org/#/c/138719/<br />
*[sushilkm] Different timeouts in configuration based per datastore<br />
**https://review.openstack.org/#/c/164640/<br />
<br/><br />
[https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]<br />
<br/><br />
[http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Meetings/TroveMeeting&diff=75843Meetings/TroveMeeting2015-03-18T15:05:54Z<p>Sushilkm: /* Trove Meeting, March 18, 2015 */</p>
<hr />
<div>= Weekly Trove Team Meeting =<br />
<br />
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt<br />
<br />
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:<br />
<br />
==== Guidelines for Writing Clear Agenda Items ====<br />
An agenda item should have a clearly defined objective.<br />
<br />
* [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.<br />
* Bad: Discuss blueprint ‘xyz’<br />
* Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.<br />
<br />
<br />
When referring to previous conversations or competing viewpoints, be sure to summarize them.<br />
<br />
Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.<br />
<br />
== Trove Meeting, March 18, 2015 ==<br />
<br />
* [SlickNik] Trove pulse update:<br />
** https://etherpad.openstack.org/p/trove-pulse-update<br />
* [SlickNik] Openstack Feature Freeze this week for kilo-3:<br />
** https://launchpad.net/trove/+milestone/kilo-3<br />
** https://etherpad.openstack.org/p/TroveKilo3Blueprints<br />
* [SlickNik] Switch from oslo namespace packages to "oslo_" style modules<br />
** https://review.openstack.org/#/c/150709/ <br />
** For context please see: http://lists.openstack.org/pipermail/openstack-dev/2015-March/059031.html<br />
*[peterstac] Come up with a strategy to deal with Mock()ing utility methods<br />
** We have several patchsets that are mocking execute_with_timeout, which can cause unexpected behaviour.<br />
** For context see: https://review.openstack.org/#/c/156486/<br />
*[sushilkm] Different timeouts in configuration based per datastore<br />
**https://review.openstack.org/#/c/164640/<br />
<br/><br />
[https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]<br />
<br/><br />
[http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Meetings/TroveMeeting&diff=74440Meetings/TroveMeeting2015-02-25T17:13:52Z<p>Sushilkm: /* Agenda for February 25 2015 */</p>
<hr />
<div>= Weekly Trove Team Meeting =<br />
<br />
We have weekly team meetings on Wednesdays at 18:00 UTC in #openstack-meeting-alt<br />
<br />
Want to add an agenda item? Please append your item to the upcoming weekly agenda while keeping in mind:<br />
<br />
==== Guidelines for Writing Clear Agenda Items ====<br />
An agenda item should have a clearly defined objective.<br />
<br />
* [owner/author/interested-party] Good: Review #xxxxx has comments on foobar.py from multiple folks and there seems to be a lack of consensus on how to solve problem ‘y’. Let’s quickly rehash the merits of both approaches in 2-5 minutes and call for a vote. Goal: choose an approach and move forward on implementation.<br />
* Bad: Discuss blueprint ‘xyz’<br />
* Bad: Revisit blueprint ‘abc’ that we talked about last week to get answers on remaining disagreements.<br />
<br />
<br />
When referring to previous conversations or competing viewpoints, be sure to summarize them.<br />
<br />
Please make sure to include your own name in the first line of the agenda item, or the name of the person who will be presenting the subject/leading the discussion.<br />
<br />
== Agenda for February 25 2015 ==<br />
<br />
* Trove pulse update:<br />
** https://etherpad.openstack.org/p/trove-pulse-update<br />
* [amrith] Need reviewers for 157140 [https://review.openstack.org/#/c/157140/]<br />
** Would like to have people look at this and consider it for merging quickly as there are other patch sets that will be impacted by it, especially the one reorganizing the guestagent code, anything that wants to add a new datastore, etc.,<br />
** There have been some comments (Simon, Ashleigh, Sushil) that I've tried to address in a reply but I would like some positive (or negative) reviews. Ok, I'd like some positive reviews ;)<br />
* [doug] Discuss 147908 [https://review.openstack.org/#/c/147908/]<br />
** There are a couple of options for how to proceed on this change and it would be good to get it into Kilo-3.<br />
* [schang] Discuss 136918 [https://review.openstack.org/#/c/136918/]<br />
** Discuss the comment thread at point #3 under the Guest Agent section. Need to decide what to do with the common code.<br />
* [amrith] Trove Liberty Mid Cycle Sprint -- Initial planning<br />
** http://doodle.com/candscrt36hg38a7<br />
** Am hoping we can nail down a date.<br />
** Currently, week of August 24th is winning.<br />
* [sushilkm] Needed reviewers for Vertica work<br />
** Looking forward for people to look at the Vertica work, the spec, trove-integration and trove patches.<br />
** The list of patchsets for the work is as follows:<br />
# trove-specs: https://review.openstack.org/151126<br />
# trove-integration: https://review.openstack.org/156149<br />
# trove: https://review.openstack.org/156486<br />
<br />
<br/><br />
[https://wiki.openstack.org/wiki/Trove/MeetingAgendaHistory#Trove_Weekly_Meeting_Agenda_History_.282015.29 Meeting Agenda History]<br />
<br/><br />
[http://eavesdrop.openstack.org/meetings/trove/2015 Meeting Chat Logs]</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Trove/Blueprints/vertica-db-support&diff=72595Trove/Blueprints/vertica-db-support2015-01-29T05:43:11Z<p>Sushilkm: /* Public API */</p>
<hr />
<div>== Description ==<br />
Add Vertica analytical database in trove datastores.<br />
<br />
== Use Case Requirements ==<br />
The implementation would provide additional feature to trove to support new datastore Vertica and specific operations for this datastore. <br />
<br />
Described operations:<br />
<br />
A. Instance creation with Vertica datastore.<br />
<br />
B. Common database operations:<br />
# Database : create, list, delete<br />
# User : create, list, delete<br />
# Revoke, grant user access<br />
<br />
C. Back-up and restore functionality for Vertica datastore.<br />
<br />
== Scope ==<br />
Implement all sections of Use Case Requirements.<br />
<br />
== Impacts ==<br />
This change would impact mainly guestagent, as new datastore will be added.<br />
<br />
=== Configuration === <br />
Configuration will be changed as per datastores. There is a proposed re-structuring for "ignoring users" as per datastore.<br />
<br />
=== Database ===<br />
<br />
This change has no impact on existing database tables.<br />
<br />
=== Public API ===<br />
No API calls are altered. Response to API calls would be similar for Vertica datastore.<br />
<br />
=== Internal API ===<br />
No change<br />
<br />
=== Guest Agent ===<br />
Vertica datastore specific guestagent code needs to be added.<br />
It will be compatible with the existing API structure and taskmanager.</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Trove/Blueprints/vertica-db-support&diff=72594Trove/Blueprints/vertica-db-support2015-01-29T05:40:56Z<p>Sushilkm: /* Use Case Requirements */</p>
<hr />
<div>== Description ==<br />
Add Vertica analytical database in trove datastores.<br />
<br />
== Use Case Requirements ==<br />
The implementation would provide additional feature to trove to support new datastore Vertica and specific operations for this datastore. <br />
<br />
Described operations:<br />
<br />
A. Instance creation with Vertica datastore.<br />
<br />
B. Common database operations:<br />
# Database : create, list, delete<br />
# User : create, list, delete<br />
# Revoke, grant user access<br />
<br />
C. Back-up and restore functionality for Vertica datastore.<br />
<br />
== Scope ==<br />
Implement all sections of Use Case Requirements.<br />
<br />
== Impacts ==<br />
This change would impact mainly guestagent, as new datastore will be added.<br />
<br />
=== Configuration === <br />
Configuration will be changed as per datastores. There is a proposed re-structuring for "ignoring users" as per datastore.<br />
<br />
=== Database ===<br />
<br />
This change has no impact on existing database tables.<br />
<br />
=== Public API ===<br />
No API calls are altered. Responce to API calls are similar for vertica Datastore.<br />
<br />
=== Internal API ===<br />
No change<br />
<br />
=== Guest Agent ===<br />
Vertica datastore specific guestagent code needs to be added.<br />
It will be compatible with the existing API structure and taskmanager.</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Trove/Blueprints/vertica-db-support&diff=72593Trove/Blueprints/vertica-db-support2015-01-29T05:39:20Z<p>Sushilkm: /* Description */</p>
<hr />
<div>== Description ==<br />
Add Vertica analytical database in trove datastores.<br />
<br />
== Use Case Requirements ==<br />
The implementation would provide an additional feature to trove which will be the support of new data store vertica and specific operations for that data store. <br />
<br />
Described operations:<br />
A. Instance creation with vertica data store.<br />
<br />
B. Common database operations:<br />
# Database : create, list, delete<br />
# User : create, list, delete<br />
# Revoke, grant user access<br />
<br />
C. back-up and restore functionality for vertica datastore.<br />
<br />
== Scope ==<br />
Implement all sections of Use Case Requirements.<br />
<br />
== Impacts ==<br />
This change would impact mainly guestagent, as new datastore will be added.<br />
<br />
=== Configuration === <br />
Configuration will be changed as per datastores. There is a proposed re-structuring for "ignoring users" as per datastore.<br />
<br />
=== Database ===<br />
<br />
This change has no impact on existing database tables.<br />
<br />
=== Public API ===<br />
No API calls are altered. Responce to API calls are similar for vertica Datastore.<br />
<br />
=== Internal API ===<br />
No change<br />
<br />
=== Guest Agent ===<br />
Vertica datastore specific guestagent code needs to be added.<br />
It will be compatible with the existing API structure and taskmanager.</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Trove/FlavorServiceType&diff=30253Trove/FlavorServiceType2013-09-17T09:38:15Z<p>Sushilkm: </p>
<hr />
<div>'''Extending Flavor API to create and delete Flavors from trove'''<br /><br />
<br /><br />
'''== Requirements ==<br />'''<br />
# Management API to add/delete flavors from trove.<br /><br />
# Categorization for '''service_type''' for a flavor created from trove.(''This categorization would be used to validate the guest vm creation and resize activities to related flavors, mapped for service.'')<br /><br />
<br /><br />
'''== Implementation ==<br />'''<br />
# In Troveclient's '''management.py''' a new class '''MgmtFlavors''' has been added with two methods for creation and deletion of flavors using the API "'''/mgmt/flavors'''" in trove.<br /><br />
# In Trove, new controller '''MgmtFlavorController''' has been added in '''trove.extensions.mgmt.flavors.service.py''' and is registered in '''trove.extensions.routes.mgmt.py'''<br /><br />
# This controller has two public methods create and delete which could be called under '''admin context''' only.<br /><br />
# Create method in controller also does a json-schema validation using the new schema added in '''trove.common.apischema.py'''<br /><br />
# Controller methods in turn calls their counter-parts from '''trove.flavor.models.py'''<br /><br />
# New class '''FlavorManage''' with 3 methods(create, delete, load_flavor) have been implemented in '''trove.flavor.models.py'''.<br />
# Class '''FlavorView''' in '''trove.flavor.views.py''' has been edited to show '''service''' for the flavors.<br />
# To keep the '''service_type''' classification, table '''service_flavors''' is created using '''trove.db.sqlalchemy.migrate_repo.versions.016_service_flavor.py''' and mapped in '''db.sqlalchemy.mappers.py''' as service_flavor.<br />
# service_flavors table is created with three columns(id, service_type, flavor_id).<br />
# New model '''ServiceFlavor''' has been created in '''trove.flavor.models.py''' to work with table service_flavors and is registered in '''trove.db.sqlalchemy.session.py'''<br />
# '''Create''' method in trove.flavor.models.py creates the flavor using '''nova client''' and creates a record in service_flavors table. '''Delete''' method deletes the flavor from nova and removes entry from trove database. '''Load_flavor''' has been written to fetch the flavor details using nova client.<br />
# Integration tests have been updated in '''trove.tests.api.flavors.py''' and unit-tests have been written as '''tests.unittests.mgmt.flavors.test_flavors_controller.py''' and '''tests.unittests.mgmt.flavors. test_flavors_models.py'''</div>Sushilkmhttps://wiki.openstack.org/w/index.php?title=Trove/FlavorServiceType&diff=30199Trove/FlavorServiceType2013-09-16T16:28:13Z<p>Sushilkm: Extending Flavor API to create and delete Flavors from trove</p>
<hr />
<div>'''Extending Flavor API to create and delete Flavors from trove'''<br /><br />
<br /><br />
'''== Requirements ==<br />'''<br />
# Management API to add/delete flavors from trove.<br /><br />
# Categorization for '''service_type''' for a flavor created from trove.(''This categorization would be used to validate the guest vm creation and resize activities to related flavors, mapped for service.'')<br /><br />
<br /><br />
'''== Implementation ==<br />'''<br />
# In Troveclient's '''management.py''' a new class '''MgmtFlavors''' has been added with two methods for creation and deletion of flavors using the API "'''/mgmt/flavors'''" in trove.<br /><br />
# In Trove, new controller '''MgmtFlavorController''' has been added in '''trove.extensions.mgmt.flavors.service.py''' and is registered in '''trove.extensions.routes.mgmt.py'''<br /><br />
# This controller has two public methods create and delete which could be called under '''admin context''' only.<br /><br />
# Create method in controller also does a json-schema validation using the new schema added in '''trove.common.apischema.py'''<br /><br />
# Controller methods in turn calls their counter-parts from '''trove.flavor.models.py'''<br /><br />
# New class '''FlavorManage''' with 3 methods(create, delete, load_flavor) have been implemented in '''trove.flavor.models.py'''.<br />
# Class '''FlavorView''' in '''trove.flavor.views.py''' has been edited to show '''service''' for the flavors.<br />
# To keep the '''service_type''' classification, table '''service_flavors''' is created using '''trove.db.sqlalchemy.migrate_repo.versions.016_service_flavor.py''' and mapped in '''db.sqlalchemy.mappers.py''' as service_flavor.<br />
# service_flavors table is created with three columns(id, service_type, flavor_id).<br />
# New model '''ServiceFlavor''' has been created in '''trove.flavor.models.py''' to work with table service_flavors and is registered in '''trove.db.sqlalchemy.session.py'''<br />
# '''Create''' method in trove.flavor.models.py creates the flavor using '''nova client''' and creates a record in service_flavors table. '''Delete''' method deletes the flavor from nova and removes entry from trove database. '''Load_flavor''' has been written to fetch the flavor details using nova client.<br />
# Integration tests have been updated in '''trove.tests.api.flavors.py''' and unit-tests have been written as '''tests.unittests.mgmt.flavors.test_flavors_controller.py''' and '''tests.unittests.mgmt.flavors. test_flavors_models.py'''<br />
# Fake implementation for nova flavor create and delete have been written in '''trove.tests.fakes.nova.py''' to support fake calls during unit-tests.</div>Sushilkm