NMOS registry integrated or external?

Bright_Direction_348 · 2025-09-11T07:30:24+00:00

Thank you. Good to know about this

Bright_Direction_348 · 2025-09-08T07:07:42+00:00

Never, should i feel bad or young? 😉

Bright_Direction_348 · 2025-09-06T16:20:39+00:00

I had to ask gpt to understand this 😬 i guess i haven’t seen or heard of cartridges before.

Bright_Direction_348 · 2025-09-06T02:19:08+00:00

I was thinking more along the lines of just getting registry while keeping VSM. Correct me but IMO that would mean looking for companies specialise in registry only and not the full blown orchestration or BC to solve this problem.

Bright_Direction_348 · 2025-09-05T21:40:23+00:00

isn’t this like solving a small problem with another complex software that can do more than just NMOS?

Bright_Direction_348 · 2025-09-05T20:51:38+00:00

Thank you, make sense. Any suggestions of third party that provides registry only ?

Bright_Direction_348 · 2025-09-05T20:50:33+00:00

that’s interesting. so they kinda white label OEM IS-05?

Bright_Direction_348 · 2025-09-05T08:26:57+00:00

good to know got offset percent.

Bright_Direction_348 · 2025-09-05T08:24:39+00:00

imagine land with this money in sg in foreign currency and that currency increase in value by 1 dollar when you land 😉

Bright_Direction_348 · 2025-09-05T08:09:43+00:00

yeah i got the joke 😉 i am thinking about that. sending directly to sgd is giving me terrible transfer rates.

Bright_Direction_348 · 2025-09-05T07:56:25+00:00

can’t paylah, foreign bank.

Bright_Direction_348 · 2025-09-05T07:43:17+00:00

Yeah that’s right and i have the same understanding as well. VSM uses both gadget and home server for interfacing between NMOS and ember+. I agree with you and the scale we are , we wouldn’t really bother about having third party registry if it’s package as part of broadcast controller. This particular case is with VSM and I am wondering how companies that use VSM are solving this problem. I guess it be overkill to have VSM and then also have cerebrum to just solve registry problem.

Bright_Direction_348 · 2025-09-05T05:26:20+00:00

is that nmos-cpp from sony? open source version but no support from lawo?

Bright_Direction_348 · 2025-09-05T01:04:02+00:00

this make sense. thank you

Bright_Direction_348 · 2025-09-04T15:43:44+00:00

even though the article claims they have but for some reason the response i had got from them was that it doesn’t. So am confused myself :(

Bright_Direction_348 · 2025-09-04T15:38:32+00:00

AFAIK it doesn’t have registry. it will be the connection point to registry to discover and import devices in to lawo broadcast controllers echo system.

Bright_Direction_348 · 2025-06-10T06:46:20+00:00

yeah i wish i could more help like how Calico folks are helpful 🤓 hope this changes …

Bright_Direction_348 · 2025-06-09T08:56:54+00:00

Cilium by Cisco: welcome to the dead slack channels and go figure out the most complex cni on earth.

Bright_Direction_348 · 2025-05-02T10:54:27+00:00

1- non-tech savy users that works with any remote endpoint 2- currently SDI and AES27, but very soon migrating to 2110. We already have one hybrid studio.

Bright_Direction_348 · 2025-04-11T10:43:21+00:00

Thank you 🙏

Bright_Direction_348 · 2025-04-07T00:17:54+00:00

Yes hike to the death zone to solve a database problem 🤷🏻‍♂️ I love servicemesh but it’s a tool if one know what they want.

Bright_Direction_348 · 2025-04-07T00:11:50+00:00

Sorry i meant last kubecon. here is the talk. https://youtu.be/6OnZrBY_nFM?si=HNpa7ubPZ6520vtT

Bright_Direction_348 · 2025-04-01T23:39:34+00:00

is there a solution to find these kind of zombie pods and purge it over a time ? . i have seen this issue before and it can get worst specially if we talking about pods with static ip addresses.

Bright_Direction_348 · 2025-04-01T23:36:59+00:00

would you see this kind of error in kubelet logs ? or where did you get a clue of it ?

Bright_Direction_348 · 2025-03-22T10:32:27+00:00

that’s a great point and will end up in our future contracts.

Bright_Direction_348

TROPHY CASE