harikrishna-patnala commented on issue #16:
URL:
https://github.com/apache/cloudstack-terraform-provider/issues/16#issuecomment-973828682
Network resource does not contain the source nat IP address, so we cannot
fetch it from network resource. Terraform provider currently have only one dat
rhtyd commented on pull request #16:
URL: https://github.com/apache/cloudstack-go/pull/16#issuecomment-973802150
Ping @davidjumani is this good to go?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to g
rhtyd merged pull request #19:
URL: https://github.com/apache/cloudstack-go/pull/19
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr..
hrak opened a new issue #16:
URL: https://github.com/apache/cloudstack-terraform-provider/issues/16
Not so much an issue but a question. In an effort to save IP address usage i
want to use the source NAT IP of a network as my public IP instead of
requesting another IP through `cloudstack_i
Agrees.
There are many users using docker, but for different goals. Depends on
requirements, the solutions are also different.
1. What OS ?
2. Use docker for packaging , demo or testing changes ?
3. Are packages ready ? official releases, nightly build or need to build
packages from source code
Hello Marcus
I was actively using docker files to deploy my own changes in kubernetes and
also to deploy multiple pods with different versions but I havent played out
with reducing the image size. I made changes to docker files to just build the
components I changed rather than building entire
Great, thanks! I'll take a look.
On Thu, Nov 18, 2021 at 5:17 AM Paul Angus wrote:
> Hi Marcus et al,
>
> This is where I had got to, to a create a containerised image of
> simulator, with options to deploy a region created by marvin (either a
> predetermined multi-zone one or a user defined one
Hi Marcus et al,
This is where I had got to, to a create a containerised image of simulator,
with options to deploy a region created by marvin (either a predetermined
multi-zone one or a user defined one)
It was based on the premise of as few layers as possible, all as small as
possible. (and
rhtyd merged pull request #20:
URL: https://github.com/apache/cloudstack-go/pull/20
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr..
psycofdj commented on pull request #21:
URL: https://github.com/apache/cloudstack-go/pull/21#issuecomment-972748801
In the current state I can't use tags lower than v2.10.0 because of other
problems, typically fixed by #7 and #19
--
This is an automated message from the Apache Git Servi
psycofdj edited a comment on pull request #21:
URL: https://github.com/apache/cloudstack-go/pull/21#issuecomment-972732987
@davidjumani are you suggesting to maintain multiple `v2.x.y` branches and
versions where each `x.y` will follow one specific version of cloudstack's api ?
--
Th
psycofdj commented on pull request #21:
URL: https://github.com/apache/cloudstack-go/pull/21#issuecomment-972732987
@davidjumani are you suggesting to maintain multiple `v2.x.y` branches and
version where each `x.y` will follow one specific version of cloudstack's api ?
--
This is an
davidjumani commented on pull request #21:
URL: https://github.com/apache/cloudstack-go/pull/21#issuecomment-972722776
@psycofdj The v2.10.0 and lower tag have int64 for the Managementserverid.
I'd prefer having tags for each version rather than partial backward
compatibility
--
This is
davidjumani commented on pull request #19:
URL: https://github.com/apache/cloudstack-go/pull/19#issuecomment-972709331
@psycofdj Can you add a test and example for this, thanks
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub
14 matches
Mail list logo
