Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrate other 1st release features #63

Merged
merged 23 commits into from
Jun 23, 2016
Merged

Integrate other 1st release features #63

merged 23 commits into from
Jun 23, 2016

Conversation

lorenzo-biava
Copy link
Contributor

@lorenzo-biava lorenzo-biava commented Jun 17, 2016

Other Features:

Also added some tests, see #56

NOTE that CMDB image data retrieval is still a stub

See #53
- Basically, for INDIGO use case, if an image with the specified name
cannot be found it means that a vanilla image must be used and later the
Ansible setup will be run. The vanilla image will be chosen according to
the other metadata information(arch, type, distro, version)

See #53
CloudProviderRanker was using MockServer, making others fail.

See #56
The message explaining the failure reason of an IM deploy was being
wrongly overwritten, and thus lost.
Added `orchestrator.url` configuration property and updated README and
Dockerfile.
Also updated related tests.
@lorenzo-biava lorenzo-biava mentioned this pull request Jun 20, 2016
11 tasks
lorenzo-biava and others added 13 commits June 20, 2016 17:59
- workflow-manager=0.0.3-FINAL
- chronos-client=0.0.1-BETA.1
Reason: need to have commands unit tests

Conflicts:
	src/main/java/it/reply/orchestrator/dto/deployment/DeploymentMessage.java
	src/main/java/it/reply/orchestrator/service/ToscaServiceImpl.java
	src/main/java/it/reply/orchestrator/service/commands/GetCMDBData.java
	src/main/java/it/reply/orchestrator/service/deployment/providers/ImServiceImpl.java
- Docker tag in image was not explicitly checked
- Other metadata were matched in case-sensitive mode

See #53
Add Image ID substitution in TOSCA template (to support multiple CP) #53
The chosen CloudProvider endpoint are generated after the choice has
been made, using the Provider and its Services from CMDB.
The CloudProviderEndpoint information is the passed through the WF in
the DeploymentMessage. It can be used by IM to generated authentication
data accordingly (NOT DONE YET).
The information is also persisted (serialized) in the Deployment for
other WFs (Update/Undeploy).

See #51
…ider

Feat/51 use selected cloud provider
@lorenzo-biava lorenzo-biava changed the title Increase unit & integration tests coverage Integrate other 1st release features Jun 23, 2016
@lorenzo-biava lorenzo-biava merged commit 1ef7b80 into master Jun 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants