How many of you are using a Development Node within a Production Site?

[stvegerton]

Just curious to see how many of you are embracing this concept and forgoing the traditional separate DEV, QA, & PROD sites?

We have 1 PROD Site with 3 Nodes:

Production: Only our published apps go here

Central: We do binary QV reloads here. All QVDs are generated in Qlikview.

Both: We develop apps here. They only synch with the central node. Published apps are here as well for load balancing.

Then we have another site just like it that we only use for patch and extension testing...

[korsikov]

I found one difference. at the Prodction site can not create new applications

[stvegerton]

‌Correct. Where you say "site", I think you mean node.

We hide the Create New App button with the Node Purpose setting in the QMC.

[korsikov]

Yes, it is. I mean node.

[Anonymous]

Hi Stephen.

when u say "Central" - i assume u r referring to Central Node? so, what nope purpose did u configure for this central node, Both or Development?

Rgds

Jim Chan

[stvegerton]

Yes, Central Node. When installing the central node, you select "create cluster". So the purpose question does not come into play if my memory is correct. That question comes up when adding rim nodes to an existing cluster.

[jim_chan]

Hi stephen, sorry.  My mistake . Central node cannot choose any node purposes unlike the rim node.

Ok u setup a central node - does this server have the share storage ? Qlikshare, where it keeps the application data?

Rim node - but u configured to "both" node purpose,  and u say it's for developer to develop apps . So how to sync the develop apps to the central node  then to the production rim node server?

Can you guide me more?

Rgds,

Jim Chan

[stvegerton]

Hi Jim,

The central node does have the storage. We put it on a D drive. BUT, our D drive is actually mapped to SAN high speed storage for the qlikshare.

We sync apps using load balancing rules. Here's one for example for our Production Node so that it only has published apps:

Name: SyncPubAppstoRimNodes

Desc:rule to sync pub apps to nodes with consume custom property

Resource Filter: App_*

Actions: Check Load Bal

Conditions: (node.@holx_node_type="consume" and !resource.stream.name.Empty())

Context: Both in Hub and QMC

[jim_chan]

Dear Stephen,

Really thank you for continuously guiding me through, please continue

Ok. the Central Node - i understood about our share storage. so this central node will run all the QS reloads(extractor.qvf, datamodelqvf file, ui.qvf file) , the scheduler is here, rite?

Then Developer Node - developer create apps here. but also share the same qlik share storage, so during installation, have to point back to your SAN storage path. rite?

- once the app has been created. it should appear in the QMC. So, admin will publish the app? am i right?

then Production Node -  it should only has shown published app. so you created a load balancing rule in the central node QMC, only sync published app to the production node.

-  i read through the rules you mentioned. but which part of it state that it will only sync to the production node?

Thanks Stephen.

Rgds

Jim Chan

[stvegerton]

Ok. the Central Node - i understood about our share storage. so this central node will run all the QS reloads(extractor.qvf, datamodelqvf file, ui.qvf file) , the scheduler is here, rite?

A: That's up to you. You can make the central node the task Master and Slave. Or you an make it the master and have your rim nodes be the slave. We've recently made the development rim node the reload slave because it is a big physical server vs. our central node, which is a small VM.

Then Developer Node - developer create apps here. but also share the same qlik share storage, so during installation, have to point back to your SAN storage path. rite? A: yes, it shares the same storage

- once the app has been created. it should appear in the QMC. So, admin will publish the app? am i right? A: Yes

then Production Node -  it should only has shown published app. so you created a load balancing rule in the central node QMC, only sync published app to the production node.

-  i read through the rules you mentioned. but which part of it state that it will only sync to the production node?

A: We created a custom property called node_type with 3 values; Central, Consume & Development. Then we add the appropriate value to the nodes. Once you do that, you can leverage the custom property in the load balancing rules.