-
Notifications
You must be signed in to change notification settings - Fork 13
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
kola: add brightbox support #484
Conversation
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
c209e1b
to
3f1dc1c
Compare
For completeness we also need |
e53791d
to
4e78735
Compare
if cloudIP != "" { | ||
plog.Infof("Adding Cloud IP to the pool: %s", cloudIP) | ||
bm.cluster.flight.cloudIPs <- cloudIP | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would move this down to be the last action of the function.
300ce86
to
1928222
Compare
All tests are passing with latest nightly:
|
platform/api/brightbox/api.go
Outdated
for _, cloudIP := range cloudIPs { | ||
// Do not remove a mapped cloud IP - otherwise, we can end up | ||
// with a server without public IP. | ||
if cloudIP.Status == cloudipstatus.Mapped { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought that makes sense to ensure that the kola run can use all available IP addrs. I guess we would need a "delete-vms" ore command to also run before this here in the Jenkins job.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Because the garbage collection comes too late when a job restarts after kola crashed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, looks good - I think for robustness we need a way of removing all leftover VMs with ore. We could also use the ore gc subcommand with a duration of 0 as workaround (if we run it before creating our image).
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
once we switch to butane, we can enable them. Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
Garbage collection can't handle yet the removal of cloud IPs - we delete cloud IPs with ore. Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
this has to run before running a test Signed-off-by: Mathieu Tortuyaux <mtortuyaux@microsoft.com>
1928222
to
0d1cebd
Compare
@pothos thanks for the review. I added a |
This PR adds Brightbox support to Mantle, in order to test Flatcar on this provider (nightly or before a release, let's discuss this later).
How to use
We first need to create the image on Brightbox.
Testing done
NOTE: