-
Notifications
You must be signed in to change notification settings - Fork 2
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
feat: Adding UPF Machine charm howto #17
base: main
Are you sure you want to change the base?
Conversation
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.
Quick first pass, I plan on trying this out today
Co-authored-by: Ghislain Bourgeois <[email protected]>
|
||
cat << EOF > terraform.tfvars | ||
machine_number = 0 | ||
model_name = "user-plane" |
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.
We need to tell user to add config options to match with environment.
As an example:
config = {
core-interface-name = "enp6s0"
access-interface-name = "enp7s0"
}
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.
+1
And it's not just about the network interfaces. The rest of the networking params needs to be here as well (unless you're super lucky to be using the addressing matching the defaults :) ).
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 agree that we should probably list most of the settings, even if we just repeat the defaults, this will make it easier to follow and tweak correctly.
|
||
- A host with a CPU supporting AVX2 and RDRAND instructions (Intel Haswell, AMD Excavator or equivalent) | ||
- [Juju][Juju] controller bootstrapped to a LXD cluster | ||
- A machine added to the Juju controller |
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.
When I add machine to the model, it stays in pending
state. Is this normal? So far, I've been only adding machines to models hosted on a separate Juju VM; and then it would go idle
state.
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.
No, it should go to active idle.
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.
As discussed, that's probably because I was trying to co-locate Juju and the UPF.
I think the requirements section should state more clearly that we need 2 machines for this how-to - one for Juju and one for UPF.
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 aggree with Bart. It is better to state that Juju and UPF needs to be located on different machines.
Co-authored-by: Bartlomiej Gmerek <[email protected]>
Description
Adds a simple howto showing deployment of machine charm with Terraform
Checklist: