Help with rebranding

Community Support
1

hi
i’m looking for 2 thing in branding
one is this :

image
image717×313 16.6 KB

i want to change the “sunstone”
the other is, how can i hide certain tabs?
image
image321×600 15.1 KB

for example the storage tab.
from what i’ve seen there isn’t a formal way to do it, but i don’t mind editing files manually, i just can’t find where to replace it among all the files used by the opennebula system (version 6.8.0)

thank you

2

Hi @Liorme !

So the rebranding of FireEdge Sunstone isn’t available in version 6.8 unfortunately, but will be included in 6.10, which is currently under development ( FireEdge Configuration — OpenNebula 6.9.80 documentation).

As for enabling/disabling certain tabs/sections/features and so on… this can all be controlled by modifying the corresponding YAML file for that tab, you can refer to the documentation for it here ( Sunstone Views — OpenNebula 6.9.80 documentation )

Best regards,
Victor

3

thank you
also, where can i set additional template logos? (for fireedge)
i found the folder, but not the file that points them

4

Hi @Liorme

Unfortunately, the ability to customize and add different template logos in FireEdge isn’t yet supported in the same way that Ruby Sunstone does it. However this is something that we will be implementing post 6.10. I have opened a new issue for it so you can track the progress of it here.

In the meantime, a hackish solution to this would be to change the images that are being referenced in FireEdge (one/src/fireedge/src/client/constants/vmTemplate.js at master · OpenNebula/one · GitHub). You can find these referenced images at this path most likely /usr/lib/one/fireedge/src/client/assets/images/logos.

Best regards,
Victor

5

thank you
inside the file it looks like this
image
so maybe i can add rows here? or it won’t work?
meaning something like
Oracle: ‘images/logos/oracle.png’,
logo1: ‘images/logos/logo1.png’,

6

Yes, you can definitely make the necessary modifications to that file as well and then re-compile FireEdge in order for them to take effect. You can refer to this part of the documentation on how to compile everything from source.

In order to try things out for yourself I suggest you clone the one repo and navigate to the fireedge subdirectory and launch it in dev mode using npm run dev. Once you have this up and running, you should be able to make any modifications you need to the codebase and it will do a hot/live-reload every time you save.

P.S. This is the folder you should add the images to when testing things out in dev mode

1 Like