2016-01-18 22:04:05 |
Devdatta Kulkarni |
bug |
|
|
added bug |
2016-01-18 22:08:06 |
Devdatta Kulkarni |
description |
We need an API to deploy a pre-built DU. This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry). This might have been put as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du> |
|
2016-01-18 22:10:14 |
Devdatta Kulkarni |
description |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry). This might have been put as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du> |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry). This might have been put as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du>
API:
POST /v1/apps/<app-id>/workflows/
{
} |
|
2016-01-18 22:22:00 |
Devdatta Kulkarni |
description |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry). This might have been put as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du>
API:
POST /v1/apps/<app-id>/workflows/
{
} |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry). This might have been put as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du>
API:
POST /v1/apps/<app-id>/workflows/
{
}
Error checking:
Check the image-id in the configured backend storage. Return an error if the image is not found in the configured storage.
What needs to happen on the back-end?
The main change is in solum-worker
solum-worker:
- If the configured storage is swift and if the configured deployer is heat, we need to generate tempURL for the specified image. The code that generates tempURL is currently in bash script called from within build-app. We will have to extract this code
- If the configured storage is glance, nothing needs to be done. |
|
2016-01-19 16:21:14 |
Devdatta Kulkarni |
description |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry). This might have been put as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du>
API:
POST /v1/apps/<app-id>/workflows/
{
}
Error checking:
Check the image-id in the configured backend storage. Return an error if the image is not found in the configured storage.
What needs to happen on the back-end?
The main change is in solum-worker
solum-worker:
- If the configured storage is swift and if the configured deployer is heat, we need to generate tempURL for the specified image. The code that generates tempURL is currently in bash script called from within build-app. We will have to extract this code
- If the configured storage is glance, nothing needs to be done. |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry) which might have been put there as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du>
API:
POST /v1/apps/<app-id>/workflows/
{
}
Error checking:
Check the image-id in the configured backend storage. Return an error if the image is not found in the configured storage.
What needs to happen on the back-end?
The main change is in solum-worker
solum-worker:
- If the configured storage is swift and if the configured deployer is heat, we need to generate tempURL for the specified image. The code that generates tempURL is currently in bash script called from within build-app. We will have to extract this code
- If the configured storage is glance, nothing needs to be done. |
|
2016-01-19 16:24:46 |
Devdatta Kulkarni |
description |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available locally or it might be available in the configured solum storage (glance/swift/docker registry) which might have been put there as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du>
API:
POST /v1/apps/<app-id>/workflows/
{
}
Error checking:
Check the image-id in the configured backend storage. Return an error if the image is not found in the configured storage.
What needs to happen on the back-end?
The main change is in solum-worker
solum-worker:
- If the configured storage is swift and if the configured deployer is heat, we need to generate tempURL for the specified image. The code that generates tempURL is currently in bash script called from within build-app. We will have to extract this code
- If the configured storage is glance, nothing needs to be done. |
We need an API to deploy a pre-built application container (DU). This is required in situations where users have already built the application's container and want to deploy it, without having to build it first. The application container might be available in the configured solum storage (glance/swift) which might have been put there as part of the previous build.
CLI Usage:
solum app deploy --build-id <build-id>
solum app deploy --image-id <glance-image-id-of-du> | <swift-id-of-du>
API:
POST /v1/apps/<app-id>/workflows/
The request body will specify the build-id or image-id which is specified on the CLI.
Error checking:
Check the image-id in the configured back-end storage. Return an error if the image is not found in the configured storage.
What needs to happen on the back-end?
The main change is in solum-worker
solum-worker:
- If the configured storage is swift and if the configured deployer is heat, we need to generate tempURL for the specified image. The code that generates tempURL is currently in bash script called from within build-app. We will have to extract this code
- If the configured storage is glance nothing needs to be done. |
|
2016-01-19 16:25:02 |
Devdatta Kulkarni |
summary |
api-to-deploy-created-du |
api-to-deploy-created-du-in-swift-glance |
|
2016-02-03 16:00:17 |
Devdatta Kulkarni |
solum: milestone |
|
next-mitaka |
|
2016-02-03 16:00:20 |
Devdatta Kulkarni |
solum: importance |
Undecided |
Medium |
|
2016-02-03 16:00:27 |
Devdatta Kulkarni |
solum: status |
New |
In Progress |
|
2016-02-03 16:00:30 |
Devdatta Kulkarni |
solum: assignee |
|
Devdatta Kulkarni (devdatta-kulkarni) |
|