Want to Know About Heat Process and OpenStack

Asked by Sourabh Jaiswal on 2015-08-28

Hi Everybody,

I am very new to openstack, I have completed some of the open stack deployments using the guides and devstack.
I want to learn about openstack in a way that I can contribute to the community.
However I had raised some of the bugs in glance and 1 of them has been marked as fixed as well but I want to know more and want to get involved more.

So if you guys can help me to what should I do to start the contribution then it would be really helpfull.

Likewise I am already doing some finding at my end I have some questions in which I want help from the community.

1. How can I trace back the flow of any api execution if had fired any curl request.
2. Which all tools should I use to start the testing and reporting.
3. From where can I find the help to create Heat templetes.
4. Is there any test planing for open stack or its just adhoc kind of thing.
5. I had tried exploring tempest test cases for heat but I got stuck while exploring the code. Is there any way by which I can dig more deep in already written cases.

Please help me out in all these confusions.

Thanks in Advance.

Sourabh Jaiswal.

Question information

English Edit question
OpenStack Heat Edit question
No assignee Edit question
Last query:
Last reply:
Qiming Teng (tengqim) said : #1

- How to contribute:


- Ask your questions

  * https://wiki.openstack.org/wiki/MailingLists
  * https://ask.openstack.org/
  * https://wiki.openstack.org/wiki/IRC

- Tracing requests

  This can be done by peeking into the 'request-id' field of a API RequestContext. If you ask this question on the mailinglist, I believe someone can give you some specific pointers.

- Document on developing/testing Heat


- Template Guide


- Heat-template Project


- Testing?

  Not quite sure what kind of tests you are referring to. Each project is doing their own unit tests and some functional tests. When putting together, there are integration tests at the gate. Tempest and Rally are projects dedicated to this purpose, although each project team is supposed to maintain their own portion of code.

- Tempest test case for Heat

  Not sure they are still very relevant. The trend, as far as I can tell, is to have each project to maintain their own functional tests.

Not sure if this answered your question. Feel free to jump onto the #heat channel on freenode IRC.

Can you help with this problem?

Provide an answer of your own, or ask Sourabh Jaiswal for more information if necessary.

To post a message you must log in.