Skip to content

Default namespace (Nuvolaris) in local installation #102

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

Open
Ersabba opened this issue Mar 8, 2025 · 4 comments
Open

Default namespace (Nuvolaris) in local installation #102

Ersabba opened this issue Mar 8, 2025 · 4 comments
Labels
enhancement New feature or request help wanted Extra attention is needed

Comments

@Ersabba
Copy link

Ersabba commented Mar 8, 2025

Ⅰ. Issue Description

Default Namespace should be Openserverless instead of Nuvolaris

Ⅱ. Describe what happened

The installation completes with following messages :

namespaces
nuvolaris
Logging in http://localhost:80 as nuvolaris
Successfully logged in as nuvolaris.
ok: whisk auth set. Run 'wsk property get --auth' to see the new value.
ok: whisk API host set to http://localhost:80
OpenServerless host and auth set successfully. You are now ready to use ops!
ok: updated package hello
ok: updated action hello/hello
"body": "hello, Nuvolaris"

Ⅲ. Describe what you expected to happen

The installation should complete with the following messages :

namespaces
openserverless
Logging in http://localhost:80 as openserverless
Successfully logged in as openserverless.
ok: whisk auth set. Run 'wsk property get --auth' to see the new value.
ok: whisk API host set to http://localhost:80
OpenServerless host and auth set successfully. You are now ready to use ops!
ok: updated package hello
ok: updated action hello/hello
"body": "hello, Openserverless"

Ⅳ. How to reproduce it (as minimally and precisely as possible)

Local installation with Docker:

  1. Install ops
  2. ops config minimal
  3. ops setup devcluster

Ⅴ. Anything else we need to know?

In the Tutorial (under review) are present html forms (Es: Index.html) containing relative url pointing to actions
with namespace openserverless that can be replaced with nuvolaris.

Ⅵ. Environment:

  • K8S Runtime and version:
  • OPS CLI version: 0.1.0-2409121919.dev
  • OS: Windows Server 2022 Version 21H2 (OS Build 20348.3207)
  • Docker Version: Docker Desktop 4.38.0 (181591)
@Ersabba Ersabba changed the title Default namespace (Nuvolaris) in local nnstallation Default namespace (Nuvolaris) in local installation Mar 8, 2025
@d4rkstar
Copy link
Contributor

d4rkstar commented Mar 9, 2025

As from the mailing list: there are a lot of references spread everywhere using the word nuvolaris. Furthermore abile attempting the rename it would be better to parametrize the namespace. Any help is greatly appreciated.

@d4rkstar d4rkstar added enhancement New feature or request help wanted Extra attention is needed labels Mar 9, 2025
@asclabs
Copy link

asclabs commented Apr 1, 2025

Hi! If no one is currently working on this, I'm interested in contributing and would like to solve this issue. Please assign it to me and let me know if there's anything I should be aware of before starting!
(I will send the signed Apache ICLA later today)

@sciabarracom
Copy link
Contributor

You are welcome but consider it is not really that easy. There are a lot of references spread in both the operator and the scripts. You need a complete grasp of all the system.

@asclabs
Copy link

asclabs commented Apr 1, 2025

Thank you for the heads-up — I truly appreciate it. I’m well aware it’s not a simple task, as I had already started investigating the issue some time ago (back in late 2024, when I tried to install Open Serveless on a local Linux server and forgot that I had already installed one of the first releases of Nuvolaris — I then realized both projects were using the same namespace!). I know it requires a full understanding of the whole system — and that’s exactly what makes this issue interesting to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

4 participants