7layerDipswitch

Anyone using Stork and Kea in prod?
I have used the Stork GUI to manage a single Kea node in a lab, and it seems quite nice now that ISC have open sourced more of the hooks with the first LTS 3.x release. I'm not sure how well it'll scale though. Anyone using in prod?
This is what interested me in it, and since then their API has only gotten better, so combined with either Custom Objects or the custom fields examples I think we could offload most of the functionality we're getting with a paid solution.

I've the Stork GUI to manage a single Kea node in a lab, and it seems quite nice now that ISC have open sourced more of the hooks with the first LTS 3.x release. Anyone successfully using in in a larger environment? Any caveats?

Do you prefer to be called homelabless, unlabbed, currently between homelabs, or???

Do you prefer to be called homelabless, or un-labbed?

I've been working through automating the initial build of some ex switches (ELS without Enhanced Automation).
I've hit some snags, it's not liking the .conf file the tftp server is offering. Is there a way to debug the process? Should I be using a SLAX file instead of trying to load the config file?
I'm trying to to create a repeatable process that I can use for multiple models (24 & 48p).

Just a vent post. Why does the u-sander have to take so long? I feel like if it had a spot to hang a couple 45lb plates I would've had several hours back. I used a Lagler Trio years ago and it was a far superior machine.

I haven't found anyone using it, and I have been having mixed results, it's an undocumented endpoint, not sure why Juniper wouldn't want us using it... Example of my code that's sorta-not-really working:

def search_marvis(my_api_key,my_org_id,some_search):
    mist_url = f"{my_base_url}labs/orgs/{my_org_id}/chatbot_converse"
    payload = {"type": "phrase", "phrase": some_search, "attempt": "first"}
    payload = str.encode(json.dumps(payload))
    try:
        response = requests.post(
        mist_url,headers={
                "Authorization": f"Token {my_api_key}",
                'Content-type': 'application/json',
            },
          

I bumped our AWX version today from 21.X to 22.3.0 via AWX Operator, and it isn't happy. We have a single node kubernetes cluster sitting behind a load balancer, with a VIP built on the load balancer. The VIP URL is vip.example.com, it terminates SSL then passes the request to AWX via the single pool member awx.example.com on port 30080 (via HTTP). I can login to awx.example.com:30080 using the expected username and password, but I'm getting `CSRF verification failed. Request aborted.` when I use the VIP.

Any help is appreciated. I haven't thus far had to configure any custom CORS config in my kub

Unfortunately all the men in the study had fallen asleep before it could be explained to them.