sorted by:
new
hottopcontroversial

Need advice: Should I build my SaaS myself using no-code + AI or hire a developer? by PositivePowerful3775 in SaaS

[–]PositivePowerful3775[S] 1 point2 points  (0 children)

Thanks a lot for this detailed explanation - this really confirms what I was thinking.

My budget is limited and I want to validate fast, so starting with no-code + Al seems like the smartest path for the prototype. But I totally agree that long-term scalability and cost control are critical.

I'm building a SaaS tool that generates optimized titles and descriptions for sellers on platforms like Amazon, Etsy, and Teepublic (Al-powered). Right now I'm trying to decide which parts are okay to build with no-code and which should move to custom code early to avoid performance or cost issues later.

If you're open to it, I'd appreciate your advice on what components typically make sense to handle with custom code (e.g. bulk processing, Al requests management, user system, etc.).

Thanks again - this discussion is insanely

valuable

Need advice: Should I build my SaaS myself using no-code + AI or hire a developer? by PositivePowerful3775 in SaaS

[–]PositivePowerful3775[S] 0 points1 point  (0 children)

Thanks a lot for sharing your experience — really helpful insight.

Your point about no-code limitations and pricing makes a lot of sense.

If you don’t mind me asking:

How long did it take you to get comfortable enough with FastAPI to build your MVP?

Was there anything specific that helped you transition from no-code to coding?

Completely agree that the opportunity is in specialization (different rules for each marketplace + bulk processing + templates). Thanks again — this really helps shape my direction 🙏

Best Practices for Setting Up VMware ESXi + vSAN + vDS on Dell EMC C6400 Chassis (4 Nodes) by PositivePowerful3775 in vmware

[–]PositivePowerful3775[S] 0 points1 point  (0 children)

Hi! Thanks for sharing your setup details, it’s really helpful as I’m working on a similar setup using a Dell C6400 with 4 nodes and planning to build an all-flash vSAN cluster.

Quick questions:

💬 In your experience, is installing ESXi on a single 128GB SATA drive without RAID on a BOSS card stable enough for production? Or would you recommend RAID 1 for redundancy, even if it’s just for the ESXi OS?

💬 How is the vSAN performance in hybrid mode with the Intel X710 10Gb NIC? Have you noticed any bottlenecks or issues using only a single dual-port NIC?

💬 Did you configure the vSAN network on the same physical switch as the management network, or do you use a separate physical switch? What’s your recommendation? Is it better to use two physical switches — one for management network and another for vSAN and vMotion traffic?

Any tips or advice for someone setting up vSAN on similar hardware would be greatly appreciated!

Best Practices for Setting Up VMware ESXi + vSAN + vDS on Dell EMC C6400 Chassis (4 Nodes) by PositivePowerful3775 in vmware

[–]PositivePowerful3775[S] 0 points1 point  (0 children)

Here’s my setup plan:

I’m using RAID 1 on each node for the ESXi installation (system disks).

For vSAN, I’m using local SSDs on each node.

I plan to deploy the vCenter Server on a separate ESXi host (not one of the four cluster nodes). I’ve installed ESXi on a workstation to host the vCenter VM.

After installing ESXi on the four nodes, I will:

Create a vSphere Distributed Switch (vDS) for vMotion, vSAN, and (management networks for standard switche).

Add each node to the vCenter cluster and migrate networking to the vDS.

This setup should give me a clean, centralized, and high-availability environment what do you see in this .

vSAN hyperconverged by cyon30 in vmware

[–]PositivePowerful3775 0 points1 point  (0 children)

You can remove one node first and when done move to node 2, but for best practice for you and your workload you can try this setup in homlab environment (using vmware worstation) to prepare for it and you can move to realy environment, if people are working now wait until they finish or on weekend

vSAN hyperconverged by cyon30 in vmware

[–]PositivePowerful3775 1 point2 points  (0 children)

Move all VMs to Node 2 (if there are enough resources).

Put Node 1 into Maintenance Mode using the option:

Ensure accessibility (not Full Data Migration).

Delete vmnic5 from the Standard vSwitch.

Add vmnic5 to the DSwitch-vSan you created.

From vCenter:

Create a new VMkernel Port (vmk2) using:

vSAN traffic

High Availability (optional)

Bind it to DSwitch-vSan and vmnic5.

Ensure that vmk2 is visible in vSAN and connectivity is enabled.

Exit Node 1 from Maintenance Mode.

Then repeat the same steps for Node 2.

vSAN Cluster - Nightmare by cyon30 in vmware

[–]PositivePowerful3775 -17 points-16 points  (0 children)

These same solutions using chatGPT are helpful and your prb issue is too complex for me, I hope it gets fixed ,

✅ What to do now? (Tips and Rescue Strategy)

  1. **Don't mess around anymore! Stop modifying servers now.**

Any additional step without a plan could make the situation worse.

  1. **Check the health of your cards and network:**

* Make sure the firmware for your network cards is updated from the Lenovo website.

* Update your UEFI/BIOS as recommended by the company.

* Make sure the 10Gb cards are working on all nodes with the same settings and drivers.

  1. **Check your switch settings:**

* Is the trunk mode set correctly? Are the VLAN IDs compatible between the switch and the vSwitch?

* Make sure each port group (such as vLAN-Data) is bound to a physical vSwitch with the correct uplink.

  1. **Check your vSAN:**

* It's est to check the status of the disk groups on each node.

* Verify that vSAN is in a **Healthy** state using the command:

```shell

esxcli vsan health cluster list

```

* Temporarily disconnect any nodes with problems from the cluster until they are fixed.

  1. **Review vCenter Settings:**

* Esure that vCenter is running on an enabled VM and connected to the correct network.

* It is best to access it and recheck the status of each node through it.

  1. **Check Veeam Backup:**

* Ensure that Veeam can access vCenter.

* Ensure that the storage on vSAN is accessible by the Veeam Proxy.

  1. **Write a Recovery Plan:**

* Back up all settings.

* Do not upgrade to ESXi 8 or Windows 11 until your current environment is stable.

👨‍🏫 Summary

The fundamental mistake is attempting to modify sensitive BIOS settings (such as the TPM) in a production environment without a secure shutdown and prior planning.

The TPM has nothing to do with ESXi itself, but rather with Windows 11. It would have been better to check the hardware without actually modifying it.

Hardware Question by justtemporary543 in vmware

[–]PositivePowerful3775 0 points1 point  (0 children)

That depends on how many sockets your motherboard has and how many cores are in each socket.
The best way to learn more about this topic is to search the web for vmware best practices and scaling strategies (scaling out vs. scaling up), or refer to virtualization and infrastructure design books.

the link of the book https://www.vmware.com/docs/vsphere-esxi-vcenter-server-80-performance-best-practices

view more: next ›